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

Was giving an SSL error, now giving a connecgt error. No firewall involved. I wonder Windows does not have ssh, so, why is vConverter using ssh.

Any help much appreciated.

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.

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

Hi,

I am unable to convert the VM to OVF format.

MyMac $ ovftool Windows\ 7.vmx
Error: Locale initialization failed.
Completed with errors

I followed the steps in other thread to fix locale issue, then I got the following error

MyMac $ ovftool Windows\ 7.vmx
Error: Failed to open file: Windows 7.vmx
MyMac $ ovftool "Windows 7.vmx"
Error: Failed to open file: Windows 7.vmx

MyMac $ ls
Windows 7-s001.vmdk    Windows 7-s005.vmdk    Windows 7-s009.vmdk    Windows 7-s013.vmdk    Windows 7-s017.vmdk    Windows 7-s021.vmdk    Windows 7.vmsd
Windows 7-s002.vmdk    Windows 7-s006.vmdk    Windows 7-s010.vmdk    Windows 7-s014.vmdk    Windows 7-s018.vmdk    Windows 7.nvram        Windows 7.vmx
Windows 7-s003.vmdk    Windows 7-s007.vmdk    Windows 7-s011.vmdk    Windows 7-s015.vmdk    Windows 7-s019.vmdk    Windows 7.plist        Windows 7.vmxf
Windows 7-s004.vmdk    Windows 7-s008.vmdk    Windows 7-s012.vmdk    Windows 7-s016.vmdk    Windows 7-s020.vmdk    Windows 7.vmdk        autoinst.flp

Regards,

Sawan Gupta

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 have a Linux VM running on fusion, and using ovftool to convert this .vmx into .ovf, then import into a ESXi 5...unfortunately having this error message.

I tried the -lax option, but doesn't help...I look into the ovf file, and found it could be this section issue

    <vmw:BootOrderSection vmw:instanceId="7" vmw:type="disk">

      <Info>Virtual hardware device boot order</Info>

    </vmw:BootOrderSection>

Anyone can share me some light to get around this...thanks

I want to edit the description filed when exporting an ova file. With export-vapp, it is pretty straightforward, just specify a parameter called “description”. like export-vapp -Description “abcd”. Is there a way to do the same thing using ovftool? Thanks.

OVF Command option:

ovftool.exe "--acceptAllEulas=true" "--name=Robo_Naren_vApp_Temp" "--datastore=fiddleback-esx2:storage1" "-dm=thin" "--network=VM-Network" "C:/appliance-main-image-8.0.0.3.0.ova" "--prop:hostname=naren.am.com" "--prop:ip=10.0.0.xx9" "--prop:netmask=255.255.252.0" "--prop:gateway=x1.3x.2xx.1" "--powerOn" "vi://root:xxxxx@1x.xx.2xx.5x/"

When i try to execute the above command i'm getting the below error.

Error:

Error: Unexpected option: --prop:ip=10.0.0.xx9

Completed with errors

OVF properties

Here's is my ovf content for the properties

      <Property ovf:key="ip" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>2. IP Address</Label>

      </Property>

      <Property ovf:key="netmask" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>3. Subnet Mask</Label>

      </Property>

      <Property ovf:key="gateway" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>4. Default Gateway</Label>

      </Property>

Using  "vSphere Client version 5.1.0"

Can anyone help me in resolving this problem ?

We have requirement to disable the option of Auto upgrade so that user cannot change it. Please provide the option which I can set at vmx file so that ovf will have the option disable.

Is there a way to disable Settings - Options - Vmware Tools - advanced - Check and upgrade Tools with powering cycling ?

Hi,

Thanks in advance for any help that can be given with this, Have been looking at rolling out .ovf VM's as part of a automation project. What we are trying to do is roll out two servers to a specific datacentre, cluster, host and Resource pool.

Script below is what we are using, it works perfectly to roll out a VM but this will only be in the root of the Datacentre.

C:\Program Files\VMware\VMware OVF Tool>ovftool -tt=vi -st=ovf --lax -n=Test --datastore=VMWARE --network="VLAN" --powerOn "Full UNC path of .ovf" "vi://Domain%5cUSER:Password@vsphere/DATACENTRE/host/Development/FULL HOST NAME/"

But when I add in the switch for Resource and the required Resource pool as seen below:

C:\Program Files\VMware\VMware OVF Tool>ovftool -tt=vi -st=ovf --lax -n=Test --datastore=VMWARE --network="VLAN" --powerOn "Full UNC path of .ovf" "vi://Domain%5cUSER:Password@vsphere/DATACENTRE/host/Development/FULL HOST NAME/Resources/Dev"

It give the following error:

Opening OVF source: Full UNC path of .ovf.ovf

Opening VI target: "vi://Domain%5cUSER:Password@vsphere/DATACENTRE/host/Development/FULL HOST NAME/Resources/Dev"

Error: No target host found in cluster that supports the chosen network/datastore/virtual hardware combination.

Possible completions:

ESXHOST 01

ESXHOST 02

ESXHOST 03

using OVFtool 3.5 with VMWare 5.0

See attached image for layout of vCentre

any help would be much appreciated.

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

Hi all,

I have a "little" question. I have installed a new vCenter 5.5 in my farm and I would like to migrate all clusters/hosts to it. In my old vcenter there are a lot of vApps. How can migrate all without problems?

Thank you very much.

Matrix

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!

I'm using the ovf tool to convert a virtual appliance to virtual machine format and getting a memory size limitation error based on the OVF source.  The source ovf file specifies 4GB of memory for guest OS:

Error:

- Virtual machine has 4,096 megabytes of memory, which is outside the range of 4 to 3,600 megabytes supported on the host.  This may be a general limitation of the host software, or specific to the guest OS selected for the virtual machine.

The work around is to edit the source ovf file and decrease the RAM size to  3 GB and conversion works fine.  But I'm curious why this limitation is occuring.  Is 3,600 MB the maximum virtual memory size supported byVMware workstation or server?

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

Experts,

I downloaded and installed VMware OVF Tool i am running Vmware Workstation 9. I am trying to figure out how to use VMware OVF Tool and create my VMs. Any help with this ?

Regards,

SD

Hi,

Am trying to export an ova from a VM using ovftool.  Something along the lines of...

ovftool --prop:Version=100 --privateKey=./id_rsa.pem --eula@=./eula.txt vi://root:mypass@myserver.mydomain.com/myVM ./myOVA.ova

Everything looks good except that I haven't been able to define the 'Product', 'Version' and 'Vendor'  that appears in the initial dialog when customers deploy the template into a running ESX / vCenter instance.

Assume this must be a v common question but have not found how this might be done from the ovftool user guide (http://www.vmware.com/support/developer/ovf/ovf301/ovftool-301-userguide.pdf) or the VMware communities.  Closest I've found is http://communities.vmware.com/thread/328504 which indicates that defining a vCenter vApp allow configurable properties to be set.

Is there any way to define these parameters via ovftool?  If not, is there a way to hack the .ova manually to define them?

Thanks in advance,

Frank.

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

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

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

Currently running:

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

Thanks.