Running OVF Tool 3.0.1 on 32 bit CentOS 6 Linux 2.6.32-279.11.1.el6.i686 (download from VMWare site md5sum was checked ok)

Tool starts up fine and is in the process of exporting a VM from one ESXi 4.1 host to another ESXi 4.1 host . 

Tool then crashes with /usr/bin/ovftool: line 23:  7629 Segmentation fault      (core dumped) "$OVFTOOL_BIN" "$@"

Hi, I'm having a problem with ovftool. I'm running ovftool against a ESXi host with a trial license. The command shows the ovf properties that I've set on the commandline, but once I'm on the virtual machine, the ovf environment is not present at all. If I do the deployment through the vSphere client, it works perfectly, same OVA file.

I see the output from ovftool:

--> /prop/ip0 = "192.168.43.159"

--> /prop/ip1 = "192.168.43.185"

but also get the warnings:

Hi- has anyone hit any problems with exporting large (e.g. > 1TB) VMs in OVA/OVF format?

I realise that you can split the files generated, but leaving aside any issues to do with the file-system on which the files reside, are there any inherent gotchas with the export mechanism or the file format that would mean it's not a good idea to rely on this for exporting large VMs...?

Thanks!

I am trying to convert a .ovf to a .vmx using the ovftool utility in terminal on OSX 10.6.8.

USING the --lax command, the result I get is as follows:

Any suggestions on how to fix this?  It seems to be a problem with ovftool itself?

Hello:

I am working in a Windows environment with ovftool 3.01.

When running the ovftool in a directory that contains an ovf and a .ovftool file, the ovftool does not seem to pick up the local configuration file.

> ovftool --help config

This will show as "Currently no local configuration options in .ovftool"

I have tried a number of permutations: ".ovftool", "<name>.ovftool", even "ovftool.cfg" on the off chance it is looking for the global name.

But none of these options work.

When I move the file to C:\Documents and Settings\$USERNAME\VMware\ovftool.cfg, which makes it global, it works just fine. So, I know the file is working.

But I am managing dozens of unique OVAs, and so having the local configuration option would be most helpful.

Am I misnaming the local config? Or is this a known bug or linux-only feature?

Thanks,

Andrew

I am trying to deploy OVAs using ovftool 3.0.1 to an ESXi 5.1 host. When deploying VCSA 5.1.0b it works as expected with the following command:

I have confirmed that I can deploy the OVA manually. I have also confirmed the MD5SUM and tried the --disableVerification flag on ovftool. Any idea what I am missing?

Hi All,

I'm unable to get ovftool to export a vm from my server that has spaces in the path to the vmx file.

Any help would be appreciated.  Thanks!

On the server:

~ # vim-cmd vmsvc/getallvms

Vmid Name             File Guest                              OS Version     Annotation

112  ar-vm            [sata3] har_vm/har_vm.vmx                rhel5_64Guest  vmx-07

16   eluefin          [sata1] eluefin/eluefin.vmx              rhel4_64Guest  vmx-07

32   igloo (RH5)      [sata0] igloo (RH5)/igloo (RH5).vmx      rhel5_64Guest  vmx-07           

When I try to export "igloo (RH5)":

C:\OVF_Tool>ovftool.exe  --compress=9 --X:logToConsole "vi://root:doublesecret@hoo.lgc.com/ha-datacenter?ds=[sata0] igloo (RH5)/igloo (RH5).vmx" F:\igloo

2013-05-23T12:55:47.089-05:00 [02908 verbose 'Default'] [SSL_DB] Using C:\Users\owjune\AppData\Roaming\VMware\ovftool_SSLDB as SSL DB

2013-05-23T12:55:47.105-05:00 [02908 verbose 'Default'] Subscribing to signal: 2 (SIGINT)

2013-05-23T12:55:47.105-05:00 [02908 verbose 'Default'] Subscribing to signal: 4 (SIGILL)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Subscribing to signal: 22 (SIGABRT)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] OvfTool Version: VMware ovftool 3.0.1 (build-801290)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Using home directory: C:\Users\owjune\AppData\Roaming\VMware\ovftool.cfg

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] OvfTool Environment:

--> /X:httpTimeout = "0"

--> /X:imageReadSize = "262144"

--> /X:logToConsole = "true"

--> /X:maxNumberOfTermSignals = "5"

--> /X:maxRedirects = "256"

--> /X:maximalDeltaConfSize = "8"

--> /X:maximalDeltaTreeSize = "6"

--> /X:progressSmoothing = "60"

--> /X:useMacNaming = "false"

--> /X:vCloudEnableGuestCustomization = "false"

--> /X:vCloudKeepTemplate = "true"

--> /X:vCloudTimeout = "3600"

--> /X:vimSessionTimeout = "600"

--> /authdPortSource = "902"

--> /authdPortTarget = "902"

--> /compress = "9"

--> /fencedMode = "bridged"

--> /prgPath = "C:\OVF_Tool"

--> /source = "vi://root:doublesecret@hoo.lgc.com/ha-datacenter?ds=[sata0] igloo (RH5)/igloo (RH5).vmx"

--> /target = "F:\igloo"

--> /vCloudTemplate = "false"

-->

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Done initializing libs

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Determining source

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Determining target

2013-05-23T12:55:47.152-05:00 [02908 verbose 'HttpConnectionPool-000000'] HttpConnectionPoolImpl created. maxPoolConnections = 20; idleTimeout = 900000000; maxOpenConnections = 20; maxConnectionAge = 0

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Getting http page: https://hoo.lgc.com/sdk/vimServiceVersions.xml

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Proxy host

2013-05-23T12:55:47.167-05:00 [00756 info 'Default'] Thread attached

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [02908 verbose 'Default'] [ViConnection] Using vim API version: 4.1

2013-05-23T12:55:47.183-05:00 [02168 info 'Default'] Thread attached

2013-05-23T12:55:47.183-05:00 [03780 info 'Default'] Thread attached

2013-05-23T12:55:47.198-05:00 [03920 info 'Default'] Thread attached

2013-05-23T12:55:47.198-05:00 [03192 info 'Default'] Thread attached

2013-05-23T12:55:47.198-05:00 [02752 info 'Default'] Thread attached

2013-05-23T12:55:47.245-05:00 [02908 verbose 'HttpConnectionPool-000001'] HttpConnectionPoolImpl created. maxPoolConnections = 1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0

2013-05-23T12:55:47.261-05:00 [02908 verbose 'Default'] Keeping VI session alive

Opening VI source: vi://root@hoo.lgc.com:443/ha-datacenter

2013-05-23T12:55:47.432-05:00 [02908 verbose 'Default'] Backtrace:

--> backtrace[00] rip 000007fef141722a

--> backtrace[01] rip 000007fef12df578

--> backtrace[02] rip 000007fef12e078e

--> backtrace[03] rip 000007fef129266b

--> backtrace[04] rip 000007feeeb0d3d1

--> backtrace[05] rip 000007fef0f703b8

--> backtrace[06] rip 000007fef0f707e9

--> backtrace[07] rip 000007fef0f8efbe

--> backtrace[08] rip 000007feee8b024e

--> backtrace[09] rip 000000013f83824d

--> backtrace[10] rip 000000013f7aca0d

--> backtrace[11] rip 000000013f7ad04a

--> backtrace[12] rip 000000013fa3a426

--> backtrace[13] rip 0000000076b5b1bd

--> backtrace[14] rip 0000000076d66861

-->

Error: vim.fault.FileNotFound

Completed with errors

I am trying to convent a vmx within vCenter server to a local vmx, i am trying with:

ovftool.exe "vi://user:password@my_vCenterserver/may_datacenter?ds=[my_datastore] my_vm/my_vm.vmx" C:\ovfs\my_vm.vmx

as the tool user guide Page 35, session "Converting a VM on ESXi or vCenter to an OVF" introduces.

But I got prompt as:

Opening VI source: vi://my_vCenterserver:443/

Error: Datacenter object not found

Completed with errors

But, i am sure the my_datacenter is INDEED exists.

Any suggestions what should i do?

Additional:

I even can NOT probe my VMX like this:

ovftool.exe vi://user:password@my_vCenterserver/my_datacenter/my_vm/my_vm.vmx

with Error:

Error: Locator does not refer to an object: vi://user:password@my_vCenterserver/my_datacenter/my_vm/my_vm.vmx

But I am very sure 'my_vmx' locates indeed there.

Hello

When using ovftool:

# ovftool file.ova file

Opening OVA source: file.ova

The manifest validates

Opening VMX target: file

Error: OVF Package is not supported by target:

- Line 60: OVF hardware element 'ResourceType' with instance ID '3': No support for the virtual hardware device type '7'.

Completed with errors

When trying to deploy ova via vCenter i got similar error:

Details: Line 60: OVF hardware element Resource Type with instance ID 3. No support for the virtual hardware device type 7.

When looking at the xml file i can see that device type 7 is related to the following:

<rasd:Address>1</rasd:Address>

<rasd:Description>VIRTIO Controller</rasd:Description>

<rasd:ElementName>VIRTIOController 0</rasd:ElementName>

<rasd:InstanceID>3</rasd:InstanceID>

<rasd:ResourceType>7</rasd:ResourceType>

How can i make it working ?

Is there any way to exclude that element from ova file ?

Thanks,

Michal

I inserted eula file in ova file by ovftool command "eula@=[filename]".

But i dont know how to insert multi laguage eula.

How do I do that with the ovftool command?

Greetings! Question in regards to OVFtool and how storage file systems are handled in VMWare.

I am using the OVFTool version 2.1.0 (Tried 3.5.0 with not much avail) to export multiple VMDK files or disks in a Virtual Machine (versions 7 and 8) to a multiple OVA files for each - at moment tool allows for consolidation of disks in a partitioned state into ONE OVA - Does anyone know of a work around or undocumented switch which can be used to create X # of virtual disks to X # of OVAs for import into another system?

Copying VMDKs is not a viable option in this case as want to remain with OVA standards.

Thank you!

Hi VMWare experts,

I am having problem with automation script because the string passed in the ovftool command uses credential vsphere.local\userXYZ instead of just userXYZ

It appears that the backsplash in the 'vsphere.local\user' cause the command line to be misinterpreted, so the automation script that calls ovftool to deploy VMs kept failing.  It erred with "cURL error of ‘couldn’t resolve hostname" even though there is nothing wrong with any hosts or hostname resolution on the network.

On a Win-based vCenter I was able to reconfigure it so that instead of requiring login user format of 'vsphere.local\userXYZ', it will now accept user = 'userXYZ'. 

With that change, ovftool.exe command string is now progress correctly and VMs are deployed. 

I could reconfigure Window-based vCenter to not use just user = userXYZ (instead of vsphere.local\account), but I could not figure out how to get vCSA to stop requiring the format of vsphere.local\userXYZ.

The string segment in the long ovftool.exe command line looked like this …

This works:

"vi://userXYZ:password@tm-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi112.cisco.com"

This does not work:

"vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com"

Is there anyway to configure vCenter Virtual Appliance to use log in format of user = userXYZ instead of user = vsphere.local\userXYZ?   Or is there some way of reformatting the string so that OS can interpret it correctly even with backsplash '\' is used in the string?

Thank you

Charles

The complete ovftool.exe command is shown below:

"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --skipManifestCheck --diskMode=thin --name=linsys2-vm1 --deploymentOption=vm_typeA --datastore=EMC-LUN1 --net:"Network Adapter 1"="VLAN 410 - 172.27.14.0/24" --net:"Network Adapter 2"="VLAN 410 - 172.27.14.0/24" --vmFolder=   --prop:cisco_hostname.Proj=linsys2-vm1 --prop:cisco_ip_0.Proj=172.27.14.135 --prop:cisco_dnsDomain.Proj=cisco.com --prop:cisco_netmask_0.Proj=255.255.255.0 --prop:cisco_gateway_0.Proj=172.27.14.1 --prop:cisco_dns1_0.Proj=172.27.200.199 --prop:cisco_dns2_0.Proj=173.36.131.10 --prop:cisco_language.Proj=English v:\ova\projectX_1.0.0.ova "vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com"

Opening OVA source: v:\ova\projectX_1.0.0.ova

The manifest does not validate

Error: cURL error: Couldn't resolve host name

Completed with errors

Installation Done!

Hi,

I am trying to deploy an. ova file using ovftool with the following command :

C:\Program Files (x86)\VMware\VMware OVF Tool>ovftool -ds=<datastore> --net:"VM Network
"=standard_trunk --net:"VM Network 2"=standard_trunk -n=g1 <<MYOVA.ova>> vi://username:password@<IPaddr>
Opening OVA source: vwlc.ova
The manifest validates
Opening VI target: vi://root@10.50.16.36:443/
Deploying to VI: vi://root@10.50.16.36:443/
Progress: 59%

Removing temporary objects and files

Transfer Failed

Error: Execution aborted

Error: Operation was canceled

Completed with errors

And it aborts with the above error.

Can anyone help me out.

Hi all,

I have a VirtualBox OVA file that I'd like to convert to vSphere with vmxnet3 driver.

I've ran my VBOX OVA file against ovftool with --lax option to avoid the "unknown hardware virtualbox-2.2" issue which produces VMX and VMDISK file.

Is there a way for OVFTOOL to change the network adapter to use vmxnet3 as opposed to "just open the VMX file and edit virtualDev section"?

Thanks,

Ed

We have a specific folder used for certain vm's that I need to deploy to.


As an example I can view the current list of vm's with:


ovftool vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms

Error: Found wrong kind of object (Folder). Possible completions are:
vmname1
vmname2
vmname3
　


Now let’s say I want to import an ovf to myvms/vmname4 I get a "Locator does not refer to an object" error.


ovftool --datastore=mydatastore --network=mynetwork vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4 newvm.ovf

Opening VI source: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Error: Locator does not refer to an object: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Completed with errors


I have tried variations of using —name and —vmfolder and changing the vi: path without success.


I can import directly to esxi and to host through vcenter but we are then having to go back into vcenter to move these vms to the correct folder.


Is there a way to get this into the "right" place up front?

Hi fellows,

                       I had deployed a virtual ESXi host on a physical ESXi and then I created an OVA file of that virtual host and then was trying to deploy the OVA after changing the IP, subnet mask and gateway properties of the OVA file. But when i used the probe mode to have a look at the class ID and other properties, I found them to be missing.

C:\Users\abhinav.srivastava>ovftool test1.ovf

OVF version:   1.0

VirtualApp:    false

Name:          vhost1

Download Size:  283.32 MB

Deployment Sizes:

  Flat disks:   25.00 GB

  Sparse disks: 325.44 MB

Networks:

  Name:        VM Network

  Description: The VM Network network

Virtual Machines:

  Name:               vhost1

  Operating System:   otherlinux64guest

  Virtual Hardware:

    Families:         vmx-08

    Number of CPUs:   2

    Cores per socket: 1

    Memory:           2.18 GB

    Disks:

      Index:          0

      Instance ID:    8

      Capacity:       25.00 GB

      Disk Types:     SCSI-lsilogic

    NICs:

      Adapter Type:   E1000

      Connection:     VM Network

So right now I am not able to change the OVA properties and deploy the virtual host. I need to do this as I want this step automated. Does anybody know why am I not able to see the properties of the OVA file. Am I going wrong somewhere. Kindly help!!

Thanks,

Abhinav

Greetings

We have developed a perl script in Linux that uses ovftools to deploy our VMs onto a vCenter installation.  We recently tried this on a new customers lab and ran into a weird error not seen before.  The issue is when ovftool is called to deploy the VM it starts fine and a see the VM created in vCenter but after a period of time I have seen a couple different errors:


One time the error was:

mtc@orchestrator-vm-pristine:~$ ovftool --noSSLVerify --net:'data=data' --net:'ipc=ipc' --net:'mgmt=mgmt' --datastore='datastore1 (4)' --name='vmme01-mgmt-1' --machineOutput "/usr/local/epc/data/working/b98d9334-c966-4ff8-a2d3-ab8bcff6a3d8/epc-os-mgmt-vm/epc-os-mgmt-vm.ovf" vi://Administrator%40vSphere.local:WaffleMan5000%21@10.30.0.130/MTS-MME-LAB/host/side-1/10.30.0.79
MANIFEST
+ <ManifestValidate valid="true"/>
PROGRESS
ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.abort</Type>
+ <LocalizedMsg>
+ Execution aborted
+ </LocalizedMsg>
+ </Error>
+ </Errors>
/usr/bin/ovftool: line 23: 2288 Segmentation fault (core dumped) "$OVFTOOL_BIN" "$@"
mtc@orchestrator-vm-pristine:~$ ovftool -v
VMware ovftool 3.5.0 (build-1274719)

After trying a couple different times I started seeing a different error, <Type> Lost connection </Type>.  This all works fine in other installations so there is something unique to this install.  Is there a document that describes the packet flow and setup for ovftools pushing the ovf/ova's out to the host?  Were are logs stored to be able to track down the issue?


 


Thanks


Eric Wolf


 

Dear all,

My company will be closed soon and we need export the finance related VM to keep for several years for audit purpose.

We are using vCenter 5.0 right now. Which format should we used for export VM? OVF or OVA?

There will have chance that the VM need import again and we hope the format will be more favour to be import in the future vCenter after  5-6 years.

Please kindly help.

Ivan

Hello, new to here and couldnt find a solution to my issuue.

Downloaded VMware OVF Tool 4.1.0

I am trying to convert GNS3 WorkBench 12.3a into an OVA to install as a guest on ESXi 5.5

GNS3WB123.vmx is the file that I'm trying to convert to OVA

I have tried following the directions from https://www.vmware.com/support/developer/ovf/ovf10/ovftool_10_userguide.pdf

I continue to get failed messages. Is there anyone here that can assist with the OVF tool so I can run GNS3 as a guest, instead of installing on a guest Windows or Linux program?

Thanks

attempting to install OVFT silently - anyone knows the trick to bypass the EULA ENTER and SPACE key entering ?