Each search for my question leads me here; I found a similar issue, but have been getting consistent failures.

I have a server VM that is in ESXi 4.1.0 502767 that I have exported to OVF Template using vSphere 5.0, then either directly in VMware Workstation 8.0.1 528992 or using ovftool 2.1.0 (build-467744) I get failures. The first failure was "target does not support CPU validation".

Following a thread I found in this list, I attempted to comment out the CpuCompatibilitySection and deleting the .mf file. This resulted in a parse error.

My next attempt was to simply delete the CpuCompatibilitySection from the .ovf file, which it appeared to do something, created a .vmx file and reported successful completion, but when trying to open the .vmx file, I get an internal error.

I also tried to do an open of the ovf file with Workstation and it appears to complete, but fails on open with again an internal error.

I've restarted Workstation and tried to open the ovf file, which appeared to complete. Including the ovftool.log and what appears to be the session log.

I'm running VMware Workstation on an HP xw6600 workstation with 8G under Windows 7 Enterprise x64.

The goal is to export a copy of a production VM server to workstation to test a software upgrade locally as I have in the past.

If there is a better way to get a copy to my workstation, please direct me to the appropriate how-to references.

Thanks!

    --alan

Ovftool need to download 2.0.1 but vmware's website when I go to the download page tells me that is not, someone can provide me the tool, thanks

Hello,

I am brand new to the OVF Tool and am currently reading the documentation and experimenting with the utility.

I would like to know if the OVF Tool is a good utility for performing VM backups (copies) in a vSphere environment.

It is not clear, if that is one of the intended uses of the OVF Tool.

How would one accomplish this (backup and restore later) with the OVF Tool command line utility?

1)  Convert vmx config file to ovf (what happens to the original vmx file and the vmdk, vmxf, nvram, etc... files?)

Once you have an ovf package, what is the best way to import it (restore the VM)?  If you use the "Deploy OVF Template" feature in vSphere client, does it launch a wizard that prompts you for all the required meta configuration?  Do you need to remember certain config settings from when you created the OVF package?

Thanks for any insight as I come up to speed with the OVF Tool.

Thanks,

Bryan

Using OVFtool 2.1 (seems the download for 3.0.1 is still broken!) to create an ovf, and I need to insert two EULAs.

The command option is --eula@=[path][filename] which is working fine for me.

But I want to have two separate EULAs from two files.  How do I do that with the ovftool command?

I am currently manually editing the xxx.ovf file and inserting the 2nd EULA by hand, which is a pain.  But it works, and when I deploy the OVF to ESXi, I get very nicely prompted for two different EULAs and I have to accept them both to continue.  Exactly as expected.

Ovftool in VMworkstation·7.0 used to convet .vmx to ovf

display error:

ovftool version  2.0

Any help with this is super appreciated!!

Thanks,

Hey,

Is anybody aware of what network flows exist when deploying an ovf file using ovftool through a vCenter?  Right now ovftool is continually erroring out with the following message:

Transfer Failed                      
Error: Network connection was lost.
Completed with errors

When watching on the vCenter I can see that the virtual machine is created but then it looks like data is never actually transferred.  So I know that the initial connection to vCenter is successful.

I'm guessing the initial connection happens with vCenter and then the data transfer occurs directly with the ESX.  Would be very appreciative if somebody could confirm this and identify the port that the data transfer happens on.

Thanks,

-Chris

I am atempting to connect to a vcloud instance to download an OVF and no matter what I cannot authenticate. Even if I manually input the userid and password it continues to prompt for them. I have creayed a userid and password specifically for this task local to the vcloud and the password and username don't conatin ANY special characters.

Any ideas?

I'm trying to use ovftool to automate OVA deployments to vCloud Director 5.1. I have installed ovftool 3.0.1 on Ubuntu and tested out some operations. Everything seems to work except that I always get a segmentation fault when I invoke a vcloud target.

Here is the logging output:

2013-04-12T09:38:22.261-07:00 [7F987B01E740 verbose 'Default'] [SSL_DB] Using /home/evan/.ovftool.ssldb as SSL DB
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 2 (SIGINT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 4 (SIGILL)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 6 (SIGABRT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 1 (SIGHUP)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 3 (SIGQUIT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 5 (SIGTRAP)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 9 (SIGKILL)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 13 (SIGPIPE)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] OvfTool Version: VMware ovftool 3.0.1 (build-801290)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Using home directory: /home/evan/.ovftool
2013-04-12T09:38:22.263-07:00 [7F987B01E740 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"
--> /fencedMode = "bridged"
--> /prgPath = "/usr/lib/vmware-ovftool"
--> /source = "vcloud://vclouddirector.intapp.net/"
--> /vCloudTemplate = "false"
-->
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Done initializing libs
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Determining source
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Determining target
2013-04-12T09:38:22.302-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.619-07:00 [7F987B01E740 verbose 'Default'] VCloud request body:
-->
2013-04-12T09:38:22.641-07:00 [7F987B01E740 verbose 'Default'] VCloud response body:
--> <?xml version="1.0" encoding="UTF-8"?>
--> <SupportedVersions xmlns="http://www.vmware.com/vcloud/versions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/versionshttp://vclouddirector/api/versions/schema/versions.xsd">
-->     <VersionInfo>
-->         <Version>1.5</Version>
-->         <LoginUrl>https://vclouddirector.intapp.net/api/sessions</LoginUrl>
   ... schema output snipped ...
-->
2013-04-12T09:38:22.648-07:00 [7F987B01E740 verbose 'Default'] VCloud version used: 5.1

The end of the strace output:

[pid 15407] munmap(0x7f8b32f7c000, 135168) = 0
[pid 15407] munmap(0x7f8b32f9d000, 135168) = 0
[pid 15407] munmap(0x7f8b3cadb000, 135168) = 0
[pid 15407] write(6, "\25\3\1\0\30B& 2\7\30\3259W0n~(4\216\375\"\35\310c\211{+\350", 29) = 29
[pid 15407] close(6)                    = 0
[pid 15407] brk(0x2c17000)              = 0x2c17000
[pid 15407] brk(0x2c38000)              = 0x2c38000
[pid 15407] write(1, "2013-04-12T09:40:54.198-07:00 [7"..., 882013-04-12T09:40:54.198-07:00 [7F8B3CB7F740 verbose 'Default'] VCloud version used: 5.1
) = 88
[pid 15407] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 15404 resumed
Process 15407 detached
[pid 15410] +++ killed by SIGSEGV (core dumped) +++
[pid 15409] +++ killed by SIGSEGV (core dumped) +++
[pid 15408] +++ killed by SIGSEGV (core dumped) +++
[pid 15411] +++ killed by SIGSEGV (core dumped) +++
<... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV && WCOREDUMP(s)}], 0, NULL) = 15407
write(2, "/usr/bin/ovftool: line 23: 15407"..., 91/usr/bin/ovftool: line 23: 15407 Segmentation fault      (core dumped) "$OVFTOOL_BIN" "$@"
) = 91
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(-1, 0x7fff27453e98, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn(0xffffffffffffffff)        = 0
rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x7f70fceb44a0}, {0x43f140, [], SA_RESTORER, 0x7f70fceb44a0}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
read(255, "", 409)                      = 0
exit_group(139)                         = ?

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?

I'm deploying OVA files to a vCenter using ovftool; it's working perfectly, but I want to go the extra mile and automatically set the hostname of the VM after it is deployed.

I found a reference to a 'hostname' property (--prop:hostname=myvm.example.com), but it doesn't actually work

Here's my command  line

ovftool --lax --acceptAllEulas --datastore=MySAN --overwrite --powerOn --vmFolder=TestFolder --diskMode=thin --powerOffTarget --prop:hostname=myvm.example.comhttp://myurl.com/path/input.ova vi://vcenteruser:password@mycenter.example.com/MyDC/host/MyD/Resources/OVFTest

So what is the proper way to do this?

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

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

We found ovftool fails to deploy a vApp instance, within which 12VMs are to be created, from an ova file, while it succeeds if the ova file contains a slimmer version ovf file (VMs' no is decreased to 8). The host where ovftool runs is in the same LAN with VCenter server so network is probably not a problem. Besides, it also succeeds to deploy the package.ova file using VSphere Client GUI.

ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

The progress bar indicating complete percentage never shows up for the 12VM-version's deployment. The verbose log shows that the upload never starts. Has anybody encountered this issue? And you'll be appreciated if you can give us a hand. And we are willing to provide our ova file to troubleshooting this issue.

Background

We generate an OVA file which contains multiple VMs. Every VM specified in the ovf file refers to either a Linux vmdk or a Win vmdk within the OVA file. With two vmdk files contained in the ova file, the file size is almost 3G. We used the above command to deploy an vApp instance, but it always fail.

The following are what we have tried.

- The machine to run ovftool always keeps in the same LAN as VCenter server. This ensures network low latency.

- We tried ovftool both with its linux's version and windows's version. Deploying the ova containing 12VMs, always fail; deploying the slimmer version with 8VMs, it works;

- The difference between 12VM and 8VM ovafiles are very simple: both has two vmdk files, file-size are almost the same(~3G). It's just the latter ovf file choose to generate small number of homogenous VMs.

The verbose logs are attached below.

ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

ŠŠŠŠŠŠŠŠ.

-->

Opening VI target:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:15:55.791Z [7FCDED7D2740 verbose 'Default'] Hostsystem used

as deploy target: vim.HostSystem:host-16

Deploying to VI:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:16:24.172Z [7FCDED7D2740 verbose 'Default'] Using file size

as progress measure

2014-01-17T08:16:24.189Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.191Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.195Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.198Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:42.512Z [7FCDBFF7D700 verbose

'HttpConnectionPool-000001'] [RemoveConnection] Connection removed; cnx:

<SSL(<io_obj p:0x00007fcde0014b00, h:-1, <TCP '0.0.0.0:0'>, <TCP

'10.146.25.129:443'>>)>; pooled: 0

work@boxbuilder:~$ lsof -i TCP

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

ovftool.b 31731 work 7u IPv4 574157 0t0 TCP

10.146.25.131:33750->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 9u IPv4 575678 0t0 TCP

10.146.25.131:33752->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 10u IPv4 574954 0t0 TCP

10.146.25.131:57555->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 11u IPv4 574159 0t0 TCP

10.146.25.131:57556->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 12u IPv4 576636 0t0 TCP

10.146.25.131:57557->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 13u IPv4 574955 0t0 TCP

10.146.25.131:57558->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 14u IPv4 574160 0t0 TCP

10.146.25.131:57559->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 15u IPv4 576637 0t0 TCP

10.146.25.131:57560->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 16u IPv4 574956 0t0 TCP

10.146.25.131:57561->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

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.


I ran into a problem when deploying an ova using ovftool with pre-installed vmware-tools. Once the appliance is booted up the IP address isn't dynamically assigned to it even though the appliance has vmware-tools pre-installed. That only happens on the ESXi free hypervisor and it works fine on the licesed version of the ESXi. I was under impression that ESXi free hypervisor provides full functionality for vmware-tools? If that's not the case, is there any other way of dynamically assigning an IP address to newly created ova?


Thanks.

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


 

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"

Hi,

I have about a dozen OVF's I'm importing into ESXi 5.5 via the Linux ovftool client. The VM's range from 5gb to 30gb and include VMDK files. I am still improrting the first one and it is taking a crazy long time. The CPU and Memory usage stays under 1% on the client, and getting up to 5% has taken me the better part of an hour. Network speeds don't seem to be an issue, I'm wired and can SCP files from the same source and destination at 30MB/s. Is there something I'm missing? please help

Hello,

I am new to OVFTool  and am having difficulty using it in Terminal on my MacBook Pro to convert an OVA (created by exporting my WinXp virtual machine from within VirtualBox), to a VMX file for use in VMWare Fusion on my MacBook Pro.

I have installed the OVFTool on my boot drive (partition) which is named "LFP OS", in the folder:  /Library/VMWare/OVFTool/.

I have the OVA file on my data drive (partition) which is named "LFP Data" in the folder: /Virtual Machines/WinXP.ova.

I want to create a virtual machine file (VMX) in the same location as the soure that I can then import into VMWare Fusion.  I have gone through the OVFTool User Guide, forums, Google etc. and cannot get it to work properly.  It may be as simple as my Terminal syntax being off.  Anyway, please help.

Here is what I used in Terminal:

LFP-MacBook-Pro:virtual machines nils$
LFP-MacBook-Pro:virtual machines nils$ pwd
/volumes/lfp data/virtual machines
LFP-MacBook-Pro:virtual machines nils$ ./Volumes/LFP\ OS/Library/VMWare/OVFTool/ovftool /Volumes/LFP\ Data/Virtual\ Machines/WinXP.ova /Volumes/LFP\ Data/Virtual\ Machines/WinXP.vmx
-bash: ./Volumes/LFP OS/Library/VMWare/OVFTool/ovftool: No such file or directory
LFP-MacBook-Pro:virtual machines nils$

Thanks for your time!

Regards,

SBNL

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.