Hi,

I'm trying to convert VM into ovf. But ovftool fails with the message:

./ovftool --powerOffSource vi://administrator:xxxxx@host/?ip=192.168.1.22 myovf.ovf
Opening VI source: vi://administrator@host/
Powering off VM: 0593498732-VM_Name
Error: File sanfs://vmfs_uuid:3c3693e8-f77a642a-1910-5c6bdcb26d3a/packages/4.1.0/vmtools/linux.iso was not found

Could you please help me with the issue above?

Thanks,

Greetings friends,

I have installed ovftool on a Linux machine with SLES 11 SP1 x86_64

I am currently experimenting on how to use ovftool, as i'm a total newbie considering it's use.

I currently have a vCenter Server 4.1, with IP 10.20.30.40. There i have the following structure:

10.20.30.40

     MyDataCenter

          Cluster1

          Cluster2

               MyVM

The datastore where the vmx is located is named NAS1

I want to convert this virtual machine to .ovf. But for starters, i would like to probe it. I'm using ovftool 2.1.0 and the user's guide says that the VMX type is supported. I thought to use vSphere Locator with Datastore (ds) query type. So, i execute the following:

ovftool vi://10.20.30.40/MyDataCenter?ds=[NAS1] MyVM/MyVM.vmx

After i'm asked for credentials, i get the following:

Please enter login information for source vi://10.20.30.40/
Username: xxxxxxx
Password: *************
Error: Curl error: Couldn't resolve host name
Completed with errors

Have you seen that before? Am i doing something wrong with the syntax? Or in general, am i using ovftool the wrong way?

Thank you for your help!

Peter

hello.

         I create a ova file from my ESXi 5.0.0 with ovftool 2.1.0-467744, then I deploy this ova file into ESXi 5.0.0 is success and work well.

But I can't deploy the same ova file into VMWare Player with ovftool 2.1.0-467744 installed. Why?

         Anybody has any idea? Thanks.

Best Regards,

I'm experiencing a coredump when attempting to deploy an OVA into vCenter 5.0.0.  I have downloaded the OVA to the Windows 7 PC locally and have run the ovftool from that path as follows:

ovftool --X:logToConsole=true --X:logLevel="verbose" --name=ovf-test --datastore=datastore-local-113 --network=VLAN-603 MVF-ver-2_OVF10.ova "vi://Administrator:**********@10.45.99.10/MitelDesignCenter/host/VLabCluster-03 (Intel G6, stand-alone)/10.45.12.113"

The verbose output looks like this:

2012-01-13T11:45:23.595-05:00 [04492 verbose 'Default'] Subscribing to signal: 2 (SIGINT)

I recently had an issue where I exported a VM as an OVF using the vSphere client, a few weeks later I needed to import the VM back into our environment and after importing I received an "Error loading Operating System" error.  I have imported and exported countless VMs as OVF files, and this is very frustrating.  I also have VMs sent to me from Government entities and I always express how they should send them as an OVF file since it makes it very easy for me to import.  Recently I had 1 out of 3 errors after the import with the same "Error loading Operating System" message.

I have tried to change the HD controller on the VM, I also created a New VM with the "custom" option and I chose the exact OS and vHardware for the VM, and I tried to use the existing .vmdk files and that does not work.  I'm just wondering if there is some simple fix out there for what I thought was a simple import and export.

I'm using ESXi 4.1 Update 2 on HP BL hardware...oh, I also have VMware Workstation 8, and I can mount the vmdk files.

I'm not sure if this is a bug or I'm missing something, but if I create a VMX using the "Other 2.6.x Linux (64-bit)" guest type (so that guestOS is "other26xlinux-64"), and then convert it to OVF via ovftool (I tried 1.0 and 2.1.0, both on Linux), the resulting XML seems wrong:

    <OperatingSystemSection ovf:id="1" vmw:osType="*other26xLinux64Guest">

Note the id of 1, and the asterisk before the osType string.  When importing the resuting OVF (ESXi & vSphere 4.1.0), the guest ends up as "Other (32-bit)", which is incorrect, but more significantly can't even boot until I change it manually to a 64-bit type.

I was expecting the OVF to contain:

   <OperatingSystemSection ovf:id="100" vmw:osType="other26xLinux64Guest">

Hand-editing the OVF to fix up the XML works fine, and I could do some sed magic to automate all this, but I'm wondering if there is a reason for this, or a more proper fix?

Thanks a lot for any help

I'm getting wildly different results while importing large OVF file into vCloud Director 1.0.1 via the ovftool than when performing the upload of the same OVF via the native JAva tool within vCloud Director itself. AS long as the file transfer compeltes through the vCD Java tool, the file is importing into vCenter correctly, and then being correctly registered within vCD.

The OVF I'm working with is 68.2 GB in size.

Below is a sanatized version of my command line and the output from the tool:

ovftool --net:"dvportgroup-48=company-Services_Internal" E:\OlioWebtest\oliowebtest.ovf "vcloud://user:password@testvcd1.company.com:443/?org=company_Services&vapp=OlioWebTest&vdc=company_Services_ALLO_vDC01&catalog=test"
Opening OVF source: E:\OlioWebtest\oliowebtest.ovf
The manifest validates
Warning: File is not referred in the manifest: oliowebtest.ovf
Opening vCloud target: vcloud://user@testvcd1.company.com:443/
Waiting for task on server .done
Deploying to vCloud: vcloud://user@testvcd1.company.com:443/
Disk Transfer Completed

Error: Invalid response from server
Completed with errors

Looking in the vCD GUI logs for the organization, I see the descriptor being processed, and the process for finalizing the upload completing, but the vApp is never added to the catalog. If I look in vCenter, I can find the VM on a valdi datastore for the org vDC and the correct resource pool in the proper state for a catalog vApp. The error "Error: Invalid response from server" is displayed immediately upon completion of the data transfer.

If I move the VM to the root of the datacenter, I can import the VM as a vApp and copy it to the caalog with no issue.

I tested with a much smaller OVF (1.3 GB), and received exactly the behavior I expected.

ovftool --net:"none=company-Services_Internal" E:\suse\descriptor.ovf "vcloud://user:password@testvcd1.company.com:443/?org=company_Services&vapp=SUSE32&vdc=company_Services_ALLO_vDC01&catalog=test"
Opening OVF source: E:\suse\descriptor.ovf
Warning: No manifest file
Opening vCloud target: vcloud://user@testvcd1.company.com:443/
Waiting for task on server .done
Deploying to vCloud: vcloud://user@testvcd1.company.com:443/
Disk Transfer Completed

Waiting for task on server ...................done
Waiting for task on server .......................................done
Waiting for task on server ..done
Completed successfully

Looking at the succesful transfer, I see an additonal action logged in the GUI logs for the organization. After the finalization record, there is a "Create virtual application" event logged on the smaller transfer that is never logged on the larger transfer.

The only item I can think of from a vCloud Director standpoint is that that vCD logon sesion timeout has expired on the large transfer long before the additional tasks are issued to vCD resulting in the invalid response. Is this the case, or is something else going on?

When looking at the vcloud-container-info.log file on the cells doing the processing for the succesful imports, I see a whole string of commands being executed in the current logged on user context.

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?

Hey all. I know I am using proper syntax, but it seems like there's a missing service running on my esx cluster. I am able to log in with vSphere, but cannot use ovftool to export a stopped server in my ESX 4.0 cluster environment.

command I am using:

ovftool vi://[username]:[password]@vi://192.168.77.111/[serverid] d:\[serveridoutput].ovf

the error I am receiving is as follows:

Error: Could not lookup host: [username]

Completed with errors

Now it's interesting because the server does seem to know that I am using a proper user/pass because if I make a mistake on the password, I am given another chance to log in, until I miss three tries. If I enter the correct password, it seems to almost connect, then fails out with the above error. I would *REALLY* appreciate some help with this guys.

Thanks in advance!

I give; I have spent too long attempting to find the magic decoder ring to get ovftool to do what I expect to be a very basic use case.

My vCenter server is win2k8 R2 node, my host node is RHEL6.3, and my guest in this case is CentOS6.3.

The vCenter server FQDN is vsphere2.foo.com.

The ESX host is las13.foo.com.

The guest is qavm1.foo.com

The Datacenter name is screwy, but appears to be passable with URI character replacements.  The name is "Foo / Bar Network" so I have been using "Foo %2f Bar Network" and quoting any URL string to deal with the spaces.

Examining the Datacenter layout in vCenter client, the path to the vm from which I want to create an OVA is

Foo / Bar Network/QA Guy/las13.foo.com/qavm1

attempting to use ovftool from either the Win2k8 server or my RHEL6.4 development machine results in the same errors.  I have perturbed the syntax of options and paths in so many ways I don't want to list them all here, but the end result is always an incorrect reference or missing object.

Might I grovel for the proper syntax to store a VM guest as an OVA?

Yes...I have devoured the manual mutiple times over...RTFM is my first tenet

Thank you all!

[root@qavm34 tmp]# ovftool --sourcetype=vmx "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Error: Unknown option: 'sourcetype'

Completed with errors

[root@qavm34 tmp]# ovftool --sourceType=vmx "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Error: Failed to open file: vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com

[root@qavm34 tmp]# ovftool --sourceType=vmx "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com/qavm1"

Error: Failed to open file: vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com/qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: administrator

Password: **********

Error: Locator does not refer to an object: vi://administrator@vsphere2.foo.com:443/Foo / Bar Network/host/las13.foo.com/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Please enter login information for source vi://vsphere2.foo.com/

Username: administrator

Password: *********

Error: Locator does not refer to an object: vi://administrator@vsphere2.foo.com:443/Foo / Bar Network/host/las13.foo.com

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/host/"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/host/

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/host"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/host

[root@qavm34 tmp]#

[root@qavm34 tmp]#

[root@qavm34 tmp]#

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Found wrong kind of object (Datacenter). Possible completions are:

  vm/

  host/

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/vm/qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/vm/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/vm/QA Guy/qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/vm/QA Guy/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com?moref=vim.vm.VirtualMachine:qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Invalid object type specified (not a ManagedEntity subtype)

[root@qavm34 tmp]# ovftool "vi://Administrator@vsphere2.foo.com?moref=vim.vm.VirtualMachine:qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Invalid object type specified (not a ManagedEntity subtype)

[root@qavm34 tmp]# ovftool "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/host/las13.foo.com

[root@qavm34 tmp]# ovftool "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network?ds=[EqualLogic] qavm1/qavm1.vmx"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: *********

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo %2f Bar Network?ds=[EqualLogic]%20qavm1/qavm1.vmx

[root@qavm34 tmp]# ovftool --version

VMware ovftool 3.0.1 (build-801290)

[root@qavm34 tmp]#

Hi,

I am getting below error while depoying a OVF template. Please suggest.

Failed to Deploy:Unable to access file: server1.vmdk.
The process cannot access the file "fullpath of vmdkfile\server1.vmdk' because it is being used by another process.

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 attempting to determine an easy method to deploy .OVA templates for quick provisioning/deployment of VM's.

I have built VM baselines using a development vSphere cluster and exported the VM to .OVA using vSphere client. Those .OVA files reside on a Linux fileserver with ovftool installed on the system and network access to future ESXi and/or vSphere clusters.

Is it possible to 'deploy' the .OVA template from the Linux fileserver directly to a remote ESXi host's datastore and/or vSphere cluster datastore? I cant get it to work.

My OVA file:

[root@centos_lab1 u0]# ls -lha

total 5.9G

drwxr-xr-x.  3 root root 4.0K Jun 28 08:48 .

dr-xr-xr-x. 24 root root 4.0K Jun 25 11:30 ..

-rw-r--r--   1 root root 5.9G Jun 24 10:01 test.ova

Attempting to deploy to ESXi host:

[root@centos_lab1 u0]# ovftool test.ova vi://root:test123@172.16.16.81

Opening OVA source: test.ova

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

Error: No target datastore specified. Possible completions:

  iSCSI-Large

  ESX1_local_datastore

  iSCSI-Equallogic

  fusionio

  Super_ISO

Completed with errors

[root@centos_lab1 u0]# ovftool test.ova vi://root:test123@172.16.16.81/iSCSI-Equallogic/

Opening OVA source: test.ova

Error: Locator does not refer to an object: vi://root@172.16.16.81:443ha-datacenter/host/esx1.lab.q9.com/Resources/iSCSI-Equallogic/

Completed with errors

Any idea what I am doing wrong here? Is what I am trying to do even possible with ovftool?

Hi all ...I'm not sure if this is the correct place to post this question and I'm hoping someone could plase advise me as to how to do this.

I created a nested ESXi 5.5b VM.The VM is not connected to a vCenter as yet and it may or may not be connected based on whether or not I want to join it to a vCenter or not.

I then set the vAPP options to enable for the VM settings.

I then set various advanced properties for the VM.

I now have a Python script (I named it test2.py) which collects the properties from an OVA during it's deployment , the script then uses the info collected from the properties and applies them in commands at the cli.

I use this info to alter things like the Hostname, DNS, IP and other info inside the VM.

This all works successfully.

I would like to have the script start/run-once at boot time after the vAPP is deployed.

How do I do this ? and where to I place the script ? so that is does not get deleted or destroyed when the ova gets created and then deployed.

Any help would be greatly appreciated.

Kind regards

Den

So long story short I'm building a self deployment install using a Kickstart script that after the install uses wget to copyy the OVA files to the local data store and then deploys the OVAs, i have the script figured out however i can't seem to get ovftool installed on ESXi 5.5, everytime i try to run it i get the following error

env: can't execute 'bash': No such file or directory

this happens even after making the file executable, here's the whole command

~ # cd /tmp

/tmp # mkdir ovf

/tmp # cd ovf/

/tmp/ovf # wget http://10.10.10.4/OVA/VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle

Connecting to 10.10.10.4 (10.10.10.4:80)

VMware-ovftool-3.5.0 100% |*******************************| 40125k  0:00:00 ETA

/tmp/ovf # chmod +x VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle

/tmp/ovf # ./VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle

env: can't execute 'bash': No such file or directory

/tmp/ovf # sh ./VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle

env: can't execute 'bash': No such file or directory

/tmp/ovf # /bin/sh ./VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle

env: can't execute 'bash': No such file or directory

I have an esxi 4.1 server that we are decommissioning as part of a move.  We've decided to archive some of the VMs that were part of a test bed, in case we need to revive them later.  I've been copying the VMs directly to a USB hard drive on my Mac with ovftool, but I've found that about half of the testbed VMs cannot be copied.  Here is an example of a failure:

wpeters$ ovftool vi://root@zeus.dvt.tachyon.net/Riverbed/VSH_markt /Volumes/Archive/VSH_markt.ova

Enter login information for source vi://zeus.dvt.tachyon.net/

Username: root

Password: *********

Opening VI source: vi://root@zeus.dvt.tachyon.net:443/Riverbed/VSH_markt

Error: vim.fault.FileNotFound

Completed with errors


 


And a success, on another VM:

wpeters$ ovftool vi://root@zeus.dvt.tachyon.net/Riverbed/VSH_250m /Volumes/Archive/VSH_250m.ova

Enter login information for source vi://zeus.dvt.tachyon.net/

Username: root

Password: *********

Opening VI source: vi://root@zeus.dvt.tachyon.net:443/Riverbed/VSH_250m

Opening OVA target: /Volumes/Archive/VSH_250m.ova

Writing OVA package: /Volumes/Archive/VSH_250m.ova

Transfer Completed                    

Completed successfully


 


Does anyone have any suggestions of what to look for?  I've started and stopped these VMs from the console, so I'm certain the storage is still available, etc.


Thanks!

Hi all.  I'm trying to archive some no-longer-used VMs with ovftool, and I've managed to save half of them.  The ovftool output looks like:

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_250m /Volumes/Archive/VSH_250m.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_250m

Opening OVA target: /Volumes/Archive/VSH_250m.ova

Writing OVA package: /Volumes/Archive/VSH_250m.ova

Transfer Completed                    

Completed successfully


 


The other half of the machines fail with the mysterious vim.fault.FileNotFound without saying which file isn't found.  I've looked at the settings for both successful and unsuccessful VMs and cannot figure out what the difference is:


 

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_markt /Volumes/Archive/VSH_markt.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_markt

Error: vim.fault.FileNotFound

Completed with errors

Hi everyone,


When I tried to launch the deploy command without indicating the host domain (scivsd05), the following error was launched: 

ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05"

2014-12-02T16:11:24.881+01:00 verbose Curl_perform error code 6 (Couldn't resolve host name)

2014-12-02T16:11:24.882+01:00 verbose CURL error buffer: Could not resolve host: scivsd05 (Domain name not found)

2014-12-02T16:11:24.882+01:00 verbose Connection error during upload

2014-12-02T16:11:24.882+01:00 verbose Connection error, sleep then retry (10 remaining)

If I indicate the host domain, then an "Locator does not refer to an object" error is launched:


ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05.domain.lan"

The name resolution for the ESXi host "scivsd05.domain.lan" is correct from both machines, the vCenter machine and the machine where OVFTool is installed.


Any idea? Thanks in advance!


 

ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05"

2014-12-02T16:11:24.881+01:00 verbose Curl_perform error code 6 (Couldn't resolve host name)

2014-12-02T16:11:24.882+01:00 verbose CURL error buffer: Could not resolve host: scivsd05 (Domain name not found)

2014-12-02T16:11:24.882+01:00 verbose Connection error during upload

2014-12-02T16:11:24.882+01:00 verbose Connection error, sleep then retry (10 remaining)

ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05.domain.lan"

I used ovftool (1.0 running in a RHEL 5.2 VM) to create an ovf of a powered off RHEL 5.1 VM.  All was successful and I can probe the OVF without issue.  However, when I try to import it as a virtual appliance using Virtual Center 2.5 Update 5 I receive:

An error occurred while parsing the OVF descriptor:  Unable to parse xml element 'Envelope'

I've attached the ovf file.

Any ideas?

I recieve the following error "- Unsupported hardware version: 3". Please assist. Converting a vmx to a ovf. Recieve error when vmx file is opened.