I'm trying to import an OVA file with settable OVF properties for configuration (product key, network configuration) into vCloud with ovftool. It seems from the documentation that I should be using the --prop option to set these values, but they don't seem to get passed through vCloud to the deployed vApp, and the system gives an error about unconfigured properties when it tries to start up. I can go in the vCloud interface and manually enter them for my vApp, but I was hoping to automate the process with ovftool.

At first I thought the issue was that the properties where at the VM level instead of the vApp level, but changing the OVA in vSphere to move the properties to the vApp itself produces the same result. Using the same command to import the OVA directly into vSphere correctly sets the properties with either version.

Is setting of OVF properties for vCloud supported by ovftool? If so, what is the correct syntax?

Currently running:

ovftool -o --acceptAllEulas --prop:productkey="XXXXX-XXXXX-XXXXX-XXXXX" --prop:ipaddress="10.146.3.1" --prop:netmask="255.255.0.0" --prop:gateway="10.146.1.254" vApp.ova vcloud://vclouddirector?org=IT&vdc=IT&catalog=IT&vapp=test1

Thanks.

I didn't find this documented anywhere else, so I wanted to note that, if you want to use windows domain accounts in the authentication process for ovftool without specifying it interactively, you must specify the \ character using %5c, as in:

ovftool --acceptAllEulas --net:nat=mgmt-net --datastore=nfs-1 --name=Ubuntu-test Ubuntu.vmwarevm/Ubuntu.vmx vi://WINDOMAIN%5cAdministrator:password@10.10.10.100/dcName/host/cluster-name

I try to deploy a OVA into a vCenter 5.5, using OVFTool with the following command:

/usr/bin/ovftool --powerOn --acceptAllEulas --noSSLVerify --skipManifestCheck --allowAllExtraConfig --X:enableHiddenProperties --deploymentOption=${VMNAME_DEPLOYMENT_SIZE} "--net:Network 1=${VMNAME_PORTGROUP}" --datastore=${VMNAME_DATASTORE} --diskMode=${VMNAME_DISK_TYPE} --name=${VMNAME_DISPLAY_NAME} --prop:vami.DNS.APPLIANCE=${VMNAME_DNS} --prop:vami.gateway.APPLIANCE=${VMNAME_GATEWAY} --prop:vami.ip0.APPLIANCE=${VMNAME_IPADDRESS} --prop:vami.netmask0.APPLIANCE=${VMNAME_NETMASK} --prop:guestinfo.cis.appliance.ssh.enabled=${ENABLE_SSH} ${VMNAME_OVA} vi:/${VCENTER_USERNAME}:${VCENTER_PASSWORD}@${VCENTER_HOSTNAME}/?dns=${ESXI_HOSTNAME}

and I got this error:

Opening VMX target: vi:/administrator*************
Error: OVF Package is not supported by target:
 - Line 768: Unsupported virtual hardware device 'VirtualSCSI'.
Warning:
 - ExtraConfig options exists in source.
Completed with errors

The OVF file has the following settings:

            <Item>
     LINE768-->   <rasd:Address xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">0</rasd:Address>
                <rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">SCSI Controller 0 - pvscsi</rasd:ElementName>
                <rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">4</rasd:InstanceID>
                <rasd:ResourceSubType>virtualSCSI</rasd:ResourceSubType>
            <rasd:ResourceType>6</rasd:ResourceType>
              </Item>

and also :

<System>
        <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
        <vssd:InstanceID>0</vssd:InstanceID>
<vssd:VirtualSystemType>vmx-07 vmx-08 vmx-09</vssd:VirtualSystemType>
      </System>

Any advice on how to fix this issue and deploy the OVA?

Thanks.

Hi,

I am trying to deploy OVA using ovftool. I see the option --network and --net available for selecting the network by name, though I was not able to find a way to assign a static IP in the ovftool command itself. Something like --ip0=10.10.10.10. Is there a way we can do this? From UI when we deploy an OVA, we have provision to provide IP, Gateway, Netmask and DNS.

Thanks

Hi all,

I am trying to implement an OVF support for some virtualization software, which is using raw images for disks. I use qemu-img to convert raw images to vmdk format. Then I use ovftool to convert ovf file into vmware instance.

When the file I have is a simple ovf descriptor + manifest + disk - all is fine, it works even if I'm using qemu-img without "compat6" option

When the disk is compressed or the OVF package is packed into OVA - there are errors being thrown. Moreover when I create OVA package with no disk, the conversion works.

Here is the fragment of results for the OVA file:

Writing VMX file: test_ova.vmx
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk Transfer Failed                      
Error: Failed to open source disk: 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Backtrace:
[00] rip 00007f09767453e4 
[01] rip 00007f09765e99d4 
[02] rip 00007f097658e038 
[03] rip 00000000004fef51 
[04] rip 000000000054aaa5 
[05] rip 000000000054ae78 
[06] rip 000000000049c41a 
[07] rip 00007f0974e62c4d 
[08] rip 000000000047ec7a 

[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Deleting file: ./test_ova-disk1.vmdk

Same fragment when I unpack OVA and then run ovftool on the .ovf file:

Writing VMX file: test_ovf.vmx
[2011-10-03 16:35:53.934 7F7E899C4720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:35:53.935 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk progress: 99%[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource: Opened 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk as diskLib source
[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Opening disk target /xcinstall-1.corp.google.com/VirtualLsiLogicController0:0
Disk Transfer Completed                   
Completed successfully

Thank you.

I'm trying to use the ovftool to import a OVA file into a ESXi server.  However I get the following error

Error: OVF Package is not supported by target:
- Line 118: Unsupported element 'Property'
Completed with errors

The related lines in the OVF file are:

    <ProductSection ovf:class="vami" ovf:instance="*******">
      <Info>Information about the installed software</Info>
      <Category>Networking Properties</Category>
118-->      <Property ovf:key="gateway" ovf:type="string" ovf:userConfigurable="true">
        <Label>Default Gateway</Label>
        <Description>The default gateway address for this VM. Leave blank if DHCP is desired.</Description>
      </Property>
      <Property ovf:key="DNS" ovf:type="string" ovf:userConfigurable="true">

Based on some initial investigation I have done I beleive this is because the ProductSection is defaulting to required="true" which forces ESXi to use these fields, however ESXi doesn't seem to support this and it errors out as shown above.

The OVA file was generated using ovftoolto export VM in a vcenter instance.  This OVA file imports fine into vcenter, but not ESXi

Is there anyway to configure ovftoolwhen run against vcenter to generate required="false" in the  ProductSection elements?

    <ProductSection ovf:class="vami" ovf:instance="*******" ovf:required="false">
   
Or some otherway to get ovftoolto export a VM from vcenter as an OVA that will import into ESXi?

ovftool 2.1, ESXi 4.1, vCenter 4.1

HI,

I'm trying to create an OVF using ovftool 3.0.1. When I issue the ovftool command from the command line I get:

Error: cURL error: Couldn't connect to server
Completed with errors

I used the following command:

/usr/bin/ovftool vi://username:password@XX.XX.XX.XX/datacenter/vm/folder/vmname /destination

I can issue the command as above without the vmname to see if I can access Vsphere and to make sure I have a valid source locator.  The command is successful and returns a list of VMs I can use. When I add the VM name to the source locator path, I get the above error. The VM is pysically about 14GB in size (that is the space alloacted).

I can use the same command to another Vpshere server and I'm successful in creating the OVF. Which leads me to think that it might be a configuration issue with this Vsphere server?

What sorts of issues can lead to the above error?

Thanks,

Fernando

I am creating ova file using VMware OVF tool .

And I want to use public Code Signing Certificate like published by Globalsign or Verisign.

But current OVF tool doucment is not introduce how to sign with timestamp.

So, when public cert is expired, just ova file is also expired.

This is problem.

Ex: Using vsphere client call deploying OVF Template, then display signing is expired.

Document

https://www.vmware.com/support/developer/ovf/ovf350/ovftool-350-userguide.pdf

Deploy an OVF Template

http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.vmadmin.doc_41/vsp_vm_guide/working_with_ovf_templates/t_import_a_virtual_appliance.html

Will signed code still be valid after the Code Signing Certificate expires?

The digital signature on code will not expire, when a timestamping service is used. A time stamp shows the validity of the certificate at the time the code was signed. Unless you’re adding additional code to your application, a new signature will not need to be applied even if the certificate used to initially sign the code expires. GlobalSign Code Signing Certificates include a time stamp feature.

https://www.globalsign.com/support/faq/objectfaq.php

ovftool is unable to deploy OVA on vCenter server 6.0

It can login into vcenter but does not accept datastore options despite having the correct value for datastore.

Appears to be some compatibility issue between vsphere 6 and ovftool 4.1

Anyone had success in doing so ?

Hi All,

I have been using ovftool to export VMs to ovf and then upload the vmdk into AWS and spin up the VM there. I have encounter my first VM that doesn't follow this pattern. The only thing I think is different is that it has two disks, as per attached disks pic. The disk1.vmdk imports fine to AWS, but try various ways (ec2-import-volume and aws ec2 import-snapshot) to import disk2.vmdk but it doesnt doesn't work. The same tasks do work for disk1.vmdk. ec2-import-volume fails wirh "ERROR: This does not appear to be a Stream Optimized VMDK. It contains invalid magic number 0" and "aws ec2 import-snapshop" failed with message "deleted ClientError: Disk validation failed [Corrupted VMDK: VMDK Descriptor does not exist.]"

It looks like disk2.vmdk is corrupt? How do I verify it or the ovf?

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -R "disk1.vmdk"

No errors were found on the virtual disk, 'disk1.vmdk'.

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -R "disk2.vmdk"

Does nothing... blank...?

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -r "disk2.vmdk" -t 5 "d2.vmdk"

Creating disk 'd2.vmdk'

Failed to convert disk: The file specified is not a virtual disk (0xf00003ebf).

disk1.vmdk:

# Disk DescriptorFile

version=1

CID=99f9dc81

parentCID=ffffffff

createType="streamOptimized"

# Extent description

RDONLY 125829120 SPARSE "generated-stream.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.deletable = "true"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "8cc93b5679040b8bf5a35c4c8e30829a"

ddb.toolsVersion = "0"

ddb.virtualHWVersion = "10"

disk2.vmdk:

# Disk DescriptorFile

version=1

CID=c6757781

parentCID=ffffffff

createType="streamOptimized"

# Extent description

RDONLY 104857600 SPARSE "generated-stream.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.deletable = "true"

ddb.geometry.cylinders = "6527"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "3c1250f5cf0a29cd8e29d0bf42bbfc30"

ddb.toolsVersion = "0"

ddb.virtualHWVersion = "10"

Hi,

I am trying to deploy OVA using ovftool. I see the option --network and --net available for selecting the network by name, though I was not able to find a way to assign a static IP in the ovftool command itself. Something like --ip0=10.10.10.10. Is there a way we can do this? From UI when we deploy an OVA, we have provision to provide IP, Gateway, Netmask and DNS.

Thanks

Hi all,

I am trying to implement an OVF support for some virtualization software, which is using raw images for disks. I use qemu-img to convert raw images to vmdk format. Then I use ovftool to convert ovf file into vmware instance.

When the file I have is a simple ovf descriptor + manifest + disk - all is fine, it works even if I'm using qemu-img without "compat6" option

When the disk is compressed or the OVF package is packed into OVA - there are errors being thrown. Moreover when I create OVA package with no disk, the conversion works.

Here is the fragment of results for the OVA file:

Writing VMX file: test_ova.vmx
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk Transfer Failed                      
Error: Failed to open source disk: 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Backtrace:
[00] rip 00007f09767453e4 
[01] rip 00007f09765e99d4 
[02] rip 00007f097658e038 
[03] rip 00000000004fef51 
[04] rip 000000000054aaa5 
[05] rip 000000000054ae78 
[06] rip 000000000049c41a 
[07] rip 00007f0974e62c4d 
[08] rip 000000000047ec7a 

[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Deleting file: ./test_ova-disk1.vmdk

Same fragment when I unpack OVA and then run ovftool on the .ovf file:

Writing VMX file: test_ovf.vmx
[2011-10-03 16:35:53.934 7F7E899C4720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:35:53.935 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk progress: 99%[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource: Opened 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk as diskLib source
[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Opening disk target /xcinstall-1.corp.google.com/VirtualLsiLogicController0:0
Disk Transfer Completed                   
Completed successfully

Thank you.

I'm trying to use the ovftool to import a OVA file into a ESXi server.  However I get the following error

Error: OVF Package is not supported by target:
- Line 118: Unsupported element 'Property'
Completed with errors

The related lines in the OVF file are:

    <ProductSection ovf:class="vami" ovf:instance="*******">
      <Info>Information about the installed software</Info>
      <Category>Networking Properties</Category>
118-->      <Property ovf:key="gateway" ovf:type="string" ovf:userConfigurable="true">
        <Label>Default Gateway</Label>
        <Description>The default gateway address for this VM. Leave blank if DHCP is desired.</Description>
      </Property>
      <Property ovf:key="DNS" ovf:type="string" ovf:userConfigurable="true">

Based on some initial investigation I have done I beleive this is because the ProductSection is defaulting to required="true" which forces ESXi to use these fields, however ESXi doesn't seem to support this and it errors out as shown above.

The OVA file was generated using ovftoolto export VM in a vcenter instance.  This OVA file imports fine into vcenter, but not ESXi

Is there anyway to configure ovftoolwhen run against vcenter to generate required="false" in the  ProductSection elements?

    <ProductSection ovf:class="vami" ovf:instance="*******" ovf:required="false">
   
Or some otherway to get ovftoolto export a VM from vcenter as an OVA that will import into ESXi?

ovftool 2.1, ESXi 4.1, vCenter 4.1

HI,

I'm trying to create an OVF using ovftool 3.0.1. When I issue the ovftool command from the command line I get:

Error: cURL error: Couldn't connect to server
Completed with errors

I used the following command:

/usr/bin/ovftool vi://username:password@XX.XX.XX.XX/datacenter/vm/folder/vmname /destination

I can issue the command as above without the vmname to see if I can access Vsphere and to make sure I have a valid source locator.  The command is successful and returns a list of VMs I can use. When I add the VM name to the source locator path, I get the above error. The VM is pysically about 14GB in size (that is the space alloacted).

I can use the same command to another Vpshere server and I'm successful in creating the OVF. Which leads me to think that it might be a configuration issue with this Vsphere server?

What sorts of issues can lead to the above error?

Thanks,

Fernando

I am creating ova file using VMware OVF tool .

And I want to use public Code Signing Certificate like published by Globalsign or Verisign.

But current OVF tool doucment is not introduce how to sign with timestamp.

So, when public cert is expired, just ova file is also expired.

This is problem.

Ex: Using vsphere client call deploying OVF Template, then display signing is expired.

Document

https://www.vmware.com/support/developer/ovf/ovf350/ovftool-350-userguide.pdf

Deploy an OVF Template

http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.vmadmin.doc_41/vsp_vm_guide/working_with_ovf_templates/t_import_a_virtual_appliance.html

Will signed code still be valid after the Code Signing Certificate expires?

The digital signature on code will not expire, when a timestamping service is used. A time stamp shows the validity of the certificate at the time the code was signed. Unless you’re adding additional code to your application, a new signature will not need to be applied even if the certificate used to initially sign the code expires. GlobalSign Code Signing Certificates include a time stamp feature.

https://www.globalsign.com/support/faq/objectfaq.php

ovftool is unable to deploy OVA on vCenter server 6.0

It can login into vcenter but does not accept datastore options despite having the correct value for datastore.

Appears to be some compatibility issue between vsphere 6 and ovftool 4.1

Anyone had success in doing so ?

Hi All,

I have been using ovftool to export VMs to ovf and then upload the vmdk into AWS and spin up the VM there. I have encounter my first VM that doesn't follow this pattern. The only thing I think is different is that it has two disks, as per attached disks pic. The disk1.vmdk imports fine to AWS, but try various ways (ec2-import-volume and aws ec2 import-snapshot) to import disk2.vmdk but it doesnt doesn't work. The same tasks do work for disk1.vmdk. ec2-import-volume fails wirh "ERROR: This does not appear to be a Stream Optimized VMDK. It contains invalid magic number 0" and "aws ec2 import-snapshop" failed with message "deleted ClientError: Disk validation failed [Corrupted VMDK: VMDK Descriptor does not exist.]"

It looks like disk2.vmdk is corrupt? How do I verify it or the ovf?

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -R "disk1.vmdk"

No errors were found on the virtual disk, 'disk1.vmdk'.

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -R "disk2.vmdk"

Does nothing... blank...?

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -r "disk2.vmdk" -t 5 "d2.vmdk"

Creating disk 'd2.vmdk'

Failed to convert disk: The file specified is not a virtual disk (0xf00003ebf).

disk1.vmdk:

# Disk DescriptorFile

version=1

CID=99f9dc81

parentCID=ffffffff

createType="streamOptimized"

# Extent description

RDONLY 125829120 SPARSE "generated-stream.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.deletable = "true"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "8cc93b5679040b8bf5a35c4c8e30829a"

ddb.toolsVersion = "0"

ddb.virtualHWVersion = "10"

disk2.vmdk:

# Disk DescriptorFile

version=1

CID=c6757781

parentCID=ffffffff

createType="streamOptimized"

# Extent description

RDONLY 104857600 SPARSE "generated-stream.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.deletable = "true"

ddb.geometry.cylinders = "6527"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "3c1250f5cf0a29cd8e29d0bf42bbfc30"

ddb.toolsVersion = "0"

ddb.virtualHWVersion = "10"

Hi,

I am trying to deploy OVA using ovftool. I see the option --network and --net available for selecting the network by name, though I was not able to find a way to assign a static IP in the ovftool command itself. Something like --ip0=10.10.10.10. Is there a way we can do this? From UI when we deploy an OVA, we have provision to provide IP, Gateway, Netmask and DNS.

Thanks

Hi all,

I am trying to implement an OVF support for some virtualization software, which is using raw images for disks. I use qemu-img to convert raw images to vmdk format. Then I use ovftool to convert ovf file into vmware instance.

When the file I have is a simple ovf descriptor + manifest + disk - all is fine, it works even if I'm using qemu-img without "compat6" option

When the disk is compressed or the OVF package is packed into OVA - there are errors being thrown. Moreover when I create OVA package with no disk, the conversion works.

Here is the fragment of results for the OVA file:

Writing VMX file: test_ova.vmx
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk Transfer Failed                      
Error: Failed to open source disk: 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Backtrace:
[00] rip 00007f09767453e4 
[01] rip 00007f09765e99d4 
[02] rip 00007f097658e038 
[03] rip 00000000004fef51 
[04] rip 000000000054aaa5 
[05] rip 000000000054ae78 
[06] rip 000000000049c41a 
[07] rip 00007f0974e62c4d 
[08] rip 000000000047ec7a 

[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Deleting file: ./test_ova-disk1.vmdk

Same fragment when I unpack OVA and then run ovftool on the .ovf file:

Writing VMX file: test_ovf.vmx
[2011-10-03 16:35:53.934 7F7E899C4720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:35:53.935 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk progress: 99%[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource: Opened 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk as diskLib source
[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Opening disk target /xcinstall-1.corp.google.com/VirtualLsiLogicController0:0
Disk Transfer Completed                   
Completed successfully

Thank you.

I'm trying to use the ovftool to import a OVA file into a ESXi server.  However I get the following error

Error: OVF Package is not supported by target:
- Line 118: Unsupported element 'Property'
Completed with errors

The related lines in the OVF file are:

    <ProductSection ovf:class="vami" ovf:instance="*******">
      <Info>Information about the installed software</Info>
      <Category>Networking Properties</Category>
118-->      <Property ovf:key="gateway" ovf:type="string" ovf:userConfigurable="true">
        <Label>Default Gateway</Label>
        <Description>The default gateway address for this VM. Leave blank if DHCP is desired.</Description>
      </Property>
      <Property ovf:key="DNS" ovf:type="string" ovf:userConfigurable="true">

Based on some initial investigation I have done I beleive this is because the ProductSection is defaulting to required="true" which forces ESXi to use these fields, however ESXi doesn't seem to support this and it errors out as shown above.

The OVA file was generated using ovftoolto export VM in a vcenter instance.  This OVA file imports fine into vcenter, but not ESXi

Is there anyway to configure ovftoolwhen run against vcenter to generate required="false" in the  ProductSection elements?

    <ProductSection ovf:class="vami" ovf:instance="*******" ovf:required="false">
   
Or some otherway to get ovftoolto export a VM from vcenter as an OVA that will import into ESXi?

ovftool 2.1, ESXi 4.1, vCenter 4.1