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

Greetings!

I'm currently trying to sign created OVA package with trusted certificate from Thawte.

This cert is valid (till 2013) and could be easily verified with openssl (`openssl verify sign.cert`) or with Windows tools.

Signing works as follows and it is okay:

ovftool --sourceType=vmx --targetType=ova --privateKey=sign.pem package.vmx package.ova

But when I try to check it with ovftool (`ovftool package.ova`) it shows:

Error: Verification of package.cert failed

Also verification of package.cert itself with openssl is also fine.

Can anybody help me on what could cause such problem?

Thanks in advance.

I don't think so and I see no option in the user manual - but just wanted to check and see if I had missed anything?

Hi All,

I have just come across ovftool and was giving a try to it. I am fairly new to VMware world.

I have a  .OVF which I exported using vSphere client 4.0. This .OVF comprises of 3 Suse Linux based virtual machines. i.e. I created a vApp on ESX (4.1) host, in this vApp I put my 3 SLES VMs and then exported it as OVF.

It has a total size of around 4.5GB.

Now I ran this command to compress this .OVF as well as gave an option to create deltadisks.

C:\> ovftool --compress=9 --makeDeltaDisks --skipManifestCheck  MyVMCluster\MyVMCluster.ovf   E:\

output:

{{{

The manifest does not validate
Generating delta disks for 2 disks (capacity 40960 MB)
Reading disks
Disk Transfer Completed

Determining optimal configuration for capacity group
Writing configuration to disk
Disk Transfer Completed

Completed successfully

}}}

Now when I checked my E:\ It had created a folder with the same name and put related files there. I saw a significant reduction in the new vmdk size. ( around 2.3GB now )

Now when I manually deploy this new ovf on vSphere client, it goes till certain %age and then flags an error:

{{{

Error uploading file to server ( E:\MyVMCluster\disk3.vmdk.gz ) Not a supported disk format ( Invalid sparse vmdk header )

}}}

and then it stops and everything rolledback.

Any pointers ?

Thanks

Nikunj

Hi,

I would like to deploy an ovf into my workstation for testing purposes. Is there any way to do that? When I try to import it, I get this:

The import failed because ... ova did not pass OVF specification conformance or virtual hardware compliance checks.

and this (after clicking the "Retry" button):

Line 149: Unsupported element 'Property'.

That specific line contains this:

<Property ovf:key="vamitimezone"

The whole "property" is

<Property ovf:key="vamitimezone"

                ovf:type="string"

                ovf:userConfigurable="true"

                ovf:value="Etc/UTC"

                ovf:qualifiers="ValueMap{&quot;Pacific/Samoa&quot;, &quot;Pacific/Auckland&quot;, &quot;US/Hawaii&quot;, &quot;US/Alaska&quot;, &quot;US/Pacific&quot;, &quot;US/Mountain&quot;, &quot;US/Central&quot;, &quot;US/Eastern&quot;, &quot;America/Caracas&quot;, &quot;America/Argentina/Buenos_Aires&quot;, &quot;America/Recife&quot;, &quot;Etc/GMT-1&quot;, &quot;Etc/UTC&quot;, &quot;Europe/London&quot;, &quot;Europe/Paris&quot;, &quot;Africa/Cairo&quot;, &quot;Europe/Moscow&quot;, &quot;Asia/Baku&quot;, &quot;Asia/Karachi&quot;, &quot;Asia/Calcutta&quot;, &quot;Asia/Dacca&quot;, &quot;Asia/Bangkok&quot;, &quot;Asia/Hong_Kong&quot;, &quot;Asia/Tokyo&quot;, &quot;Australia/Sydney&quot;, &quot;Pacific/Noumea&quot;, &quot;Pacific/Fiji&quot;}">

        <Label ovf:msgid="application.timezone.label"/>

        <Description ovf:msgid="application.timezone.description"/>

      </Property>

It is a 2 VMs OVF (vcOPS). I tried creating the VM and adding the vmdks but there are so many OS errors during OS start-up that I think that maybe (hopefully) there's an easier way to do this.

Any help is more than welcome

Regards,

elgreco81

Hi Everyone,

I was trying to deploy a VM using the ovftool, I thought I would use the properties which are thrown from a "probe" of the OVA file.

ovftool http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

Properties:

  ClassId:     vami

  Key:         gateway

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Default Gateway

  Type:        string

  Description: The default gateway address for this VM. Leave blank if DHCP is

               desired.

  ClassId:     vami

  Key:         DNS

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       DNS

  Type:        string

  Description: The domain name servers for this VM (comma separated). Leave

               blank if DHCP is desired.

  ClassId:     vami

  Key:         ip0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 IP Address

  Type:        string

  Description: The IP address for this interface. Leave blank if DHCP is

               desired.

  ClassId:     vami

  Key:         netmask0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 Netmask

  Type:        string

After having made sure that such properties exists from the probe, I tried to use them to give the VM a static IP post deployment, automatically.

ovftool --datastore="31_datastore" --acceptAllEulas --ipAllocationPolicy=fixedPolicy --name="vPAS_31_1" --powerOn --prop:ip0="172.16.121.115" --prop:netmask0="255.255.0.0" --prop:DNS="172.16.1.10" --prop:gateway="172.16.1.1" http://server/vpas/6.0.0/latest/vPAS-installer.ova vi://root:password@172.16.121.31/

Opening OVA source: http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

The manifest validates

Opening VI target: vi://root@172.16.121.31:443/

Deploying to VI: vi://root@172.16.121.31:443/

Transfer Completed                   

Powering on VM: vPAS_31_1

Warning:

- OVF property with key: 'DNS' does not exists.

- OVF property with key: 'gateway' does not exists.

- OVF property with key: 'ip0' does not exists.

- OVF property with key: 'netmask0' does not exists.

Completed successfully

Can someone please explain me whether this is a common problem ( from VMware ) or something I am doing wrong?

Thanks,

I want to set some properties to ovf files.

I use ovftool as bellow:

ovftool --prop:ip=10.32.23.123 --prop:dns=255.255.254.0

when this command has been executed without error showing, I still cannot see the property of ovf files.

Then I used ovftool myovffile.ovf

I still can not see the property I want to set.

what should I do?

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.

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

Greetings!

I'm currently trying to sign created OVA package with trusted certificate from Thawte.

This cert is valid (till 2013) and could be easily verified with openssl (`openssl verify sign.cert`) or with Windows tools.

Signing works as follows and it is okay:

ovftool --sourceType=vmx --targetType=ova --privateKey=sign.pem package.vmx package.ova

But when I try to check it with ovftool (`ovftool package.ova`) it shows:

Error: Verification of package.cert failed

Also verification of package.cert itself with openssl is also fine.

Can anybody help me on what could cause such problem?

Thanks in advance.

I don't think so and I see no option in the user manual - but just wanted to check and see if I had missed anything?

Hi All,

I have just come across ovftool and was giving a try to it. I am fairly new to VMware world.

I have a  .OVF which I exported using vSphere client 4.0. This .OVF comprises of 3 Suse Linux based virtual machines. i.e. I created a vApp on ESX (4.1) host, in this vApp I put my 3 SLES VMs and then exported it as OVF.

It has a total size of around 4.5GB.

Now I ran this command to compress this .OVF as well as gave an option to create deltadisks.

C:\> ovftool --compress=9 --makeDeltaDisks --skipManifestCheck  MyVMCluster\MyVMCluster.ovf   E:\

output:

{{{

The manifest does not validate
Generating delta disks for 2 disks (capacity 40960 MB)
Reading disks
Disk Transfer Completed

Determining optimal configuration for capacity group
Writing configuration to disk
Disk Transfer Completed

Completed successfully

}}}

Now when I checked my E:\ It had created a folder with the same name and put related files there. I saw a significant reduction in the new vmdk size. ( around 2.3GB now )

Now when I manually deploy this new ovf on vSphere client, it goes till certain %age and then flags an error:

{{{

Error uploading file to server ( E:\MyVMCluster\disk3.vmdk.gz ) Not a supported disk format ( Invalid sparse vmdk header )

}}}

and then it stops and everything rolledback.

Any pointers ?

Thanks

Nikunj

Hi,

I would like to deploy an ovf into my workstation for testing purposes. Is there any way to do that? When I try to import it, I get this:

The import failed because ... ova did not pass OVF specification conformance or virtual hardware compliance checks.

and this (after clicking the "Retry" button):

Line 149: Unsupported element 'Property'.

That specific line contains this:

<Property ovf:key="vamitimezone"

The whole "property" is

<Property ovf:key="vamitimezone"

                ovf:type="string"

                ovf:userConfigurable="true"

                ovf:value="Etc/UTC"

                ovf:qualifiers="ValueMap{&quot;Pacific/Samoa&quot;, &quot;Pacific/Auckland&quot;, &quot;US/Hawaii&quot;, &quot;US/Alaska&quot;, &quot;US/Pacific&quot;, &quot;US/Mountain&quot;, &quot;US/Central&quot;, &quot;US/Eastern&quot;, &quot;America/Caracas&quot;, &quot;America/Argentina/Buenos_Aires&quot;, &quot;America/Recife&quot;, &quot;Etc/GMT-1&quot;, &quot;Etc/UTC&quot;, &quot;Europe/London&quot;, &quot;Europe/Paris&quot;, &quot;Africa/Cairo&quot;, &quot;Europe/Moscow&quot;, &quot;Asia/Baku&quot;, &quot;Asia/Karachi&quot;, &quot;Asia/Calcutta&quot;, &quot;Asia/Dacca&quot;, &quot;Asia/Bangkok&quot;, &quot;Asia/Hong_Kong&quot;, &quot;Asia/Tokyo&quot;, &quot;Australia/Sydney&quot;, &quot;Pacific/Noumea&quot;, &quot;Pacific/Fiji&quot;}">

        <Label ovf:msgid="application.timezone.label"/>

        <Description ovf:msgid="application.timezone.description"/>

      </Property>

It is a 2 VMs OVF (vcOPS). I tried creating the VM and adding the vmdks but there are so many OS errors during OS start-up that I think that maybe (hopefully) there's an easier way to do this.

Any help is more than welcome

Regards,

elgreco81

Hi Everyone,

I was trying to deploy a VM using the ovftool, I thought I would use the properties which are thrown from a "probe" of the OVA file.

ovftool http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

Properties:

  ClassId:     vami

  Key:         gateway

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Default Gateway

  Type:        string

  Description: The default gateway address for this VM. Leave blank if DHCP is

               desired.

  ClassId:     vami

  Key:         DNS

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       DNS

  Type:        string

  Description: The domain name servers for this VM (comma separated). Leave

               blank if DHCP is desired.

  ClassId:     vami

  Key:         ip0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 IP Address

  Type:        string

  Description: The IP address for this interface. Leave blank if DHCP is

               desired.

  ClassId:     vami

  Key:         netmask0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 Netmask

  Type:        string

After having made sure that such properties exists from the probe, I tried to use them to give the VM a static IP post deployment, automatically.

ovftool --datastore="31_datastore" --acceptAllEulas --ipAllocationPolicy=fixedPolicy --name="vPAS_31_1" --powerOn --prop:ip0="172.16.121.115" --prop:netmask0="255.255.0.0" --prop:DNS="172.16.1.10" --prop:gateway="172.16.1.1" http://server/vpas/6.0.0/latest/vPAS-installer.ova vi://root:password@172.16.121.31/

Opening OVA source: http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

The manifest validates

Opening VI target: vi://root@172.16.121.31:443/

Deploying to VI: vi://root@172.16.121.31:443/

Transfer Completed                   

Powering on VM: vPAS_31_1

Warning:

- OVF property with key: 'DNS' does not exists.

- OVF property with key: 'gateway' does not exists.

- OVF property with key: 'ip0' does not exists.

- OVF property with key: 'netmask0' does not exists.

Completed successfully

Can someone please explain me whether this is a common problem ( from VMware ) or something I am doing wrong?

Thanks,

I want to set some properties to ovf files.

I use ovftool as bellow:

ovftool --prop:ip=10.32.23.123 --prop:dns=255.255.254.0

when this command has been executed without error showing, I still cannot see the property of ovf files.

Then I used ovftool myovffile.ovf

I still can not see the property I want to set.

what should I do?

I'm having some trouble getting the vSphere Client to import my OVF's. When using the vSphere Client, I successfully walk through the wizard to "Deploy OVF Template" then get the following error:

"Failed to deploy OVF package: The remote server returned an error: (500) Internal Server Error"

Sometimes the error is a timeout error but this is very infrequent (I failed to capture the output).

In the Event log I see this error roughly 2 minutes after the import:

Deploy OVF template

MyVA

The task was

canceled by

a user.

ESXUSR

virtcent-dev.my.com

10/20/2009 12:13:09 PM

10/20/2009 12:13:09 PM

10/20/2009 12:15:37 PM

I can convert my OVF back to VMX format.

VMware ovftool 1.0.0 (build-166674). The command I'm executing is simply: ovftool "xxxx.vmx" "yyy.ovf"

It looks like a possible timeout issue on the cliet side, but I've reset the timeout (Edit-&gt;Client Settings-&gt;Client-Server command timeout = 600).  This didn't seem to have any impact on the problem.

Thanks for any help.

Hello,

I am using vSphere ESX (4 or 5).

I am writing automatic scripts using esxcfg and ovftool (on windows) commands.

I have some questions:

1. How can i create Resource Pool's? (if it cannot be done using ovftool, is there another way? maybe using esxcfg?)

2. What is the exact syntax of ovftool to deploy under that Resource Pool?

I am looking for something like this:

ovftool --noImageFiles -ds=dsName --net:"Network1"="Network2" --name=MyVM "C:/MyVM.ovf" "vi://user:password@192.168.1.1/Resource/myResource"

or anything else that can help.

Thanks!

erelh

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.