Hi,

  Now I have a problem with OVFtool. I want to create a virtual machine on an ESX 3.5 server, but i don't want to use the OVF tool and the VI client. I know that there is a managed object called "OvfManager" in the VMWare API, but this object is supported only by vSphere 4.0 and higher. Is there any method that I can use the API to create the VM from the OVF file, without using the OVFtool? Thanks.

Is there a way to map network devices that are both associated with "VM Network" in the ova to different networks on the target?  The ova contains only "VM Network", but I would like to put one interface on "NET_A" and one on "NET_B".

I need access to my deployed virtual machine's serial console, not through a GUI window, but through ssh or telnet.  I finally found how to define a serial console so that I can telnet in, which is perfect, but now I'd like to automate the defining of that serial device without using the vSphere Client GUI.

I can define my serial port from the vSphere Client GUI after deploying my VM by powering off the VM, Edit Settings -> Add a Serial Port, check "Connect via Network" -> Network Backing -> Server (VM listens for connections), Port URI = telnet://10.36.0.85:7001, where 10.36.0.85 is my ESXi 4.1 server's IP address and 7001 is a random port.  When I power on my VM, I can telnet 10.36.0.85 7001 from a remote system and viola, I have serial console/terminal access.

In the vmx file, I can see

  serial0.present = "TRUE"

  serial0.yieldOnMsrRead = "TRUE"

  serial0.fileType = "network"

  serial0.fileName = "telnet://10.36.0.85:7001"

The question is, how can I define the above either in the ovf file before I deploy, as I deploy (I'm using ovftool from a remote system), or via a remote command afterwards, e.g. a vSphere CLI command?  When I try exporting the ovf template from the vSphere client, I get "Device 'Serial port 1' cannot be exported."

Hi , there !

i got problem when i deploy a .ova file , when the process of deploying is around 98 99 % an error comes say u can't go any farther !!!

this is a complete log of what it says !!!

******************************************************************

C:\Documents and Settings\SOLMATE\Desktop>"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --X:logToConsole "K:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram).ova" k:\'

"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe"' is not recognized as an internal or external command,operable program or batch file.

C:\Documents and Settings\SOLMATE\Desktop>"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --X:logToConsole "K:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200
G -8G(Ram).ova" k:\
2011-09-28T11:38:38.318+03:30 [05000 verbose 'Default'] Subscribing to signal: 2 (SIGINT)
2011-09-28T11:38:38.318+03:30 [05000 verbose 'Default'] Subscribing to signal: 4 (SIGILL)
2011-09-28T11:38:38.318+03:30 [05000 verbose 'Default'] Subscribing to signal: 22 (SIGABRT)
2011-09-28T11:38:38.318+03:30 [05000 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)
2011-09-28T11:38:38.318+03:30 [05000 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)
2011-09-28T11:38:38.318+03:30 [05000 verbose 'Default'] [ovfTool.cpp] Using home directory C:\Documents and Settings\SOLMATE\Application Data\VMware\ovftool.cfg
2011-09-28T11:38:38.318+03:30 [05000 verbose 'Default'] [ovfTool.cpp] OvfTool Environment:
--> /X:httpTimeout = "600"
--> /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:vCloudKeepTemplate = "true"
--> /X:vCloudTimeout = "3600"
--> /X:vimSessionTimeout = "600"
--> /authdPortSource = "902"
--> /authdPortTarget = "902"
--> /fencedMode = "bridged"
--> /prgPath = "C:\Program Files\VMware\VMware OVF Tool"
--> /source = "K:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram).ova"
--> /target = "k:\"
-->
2011-09-28T11:38:38.396+03:30 [05000 verbose 'Default'] [ovfTool.cpp] Done initializing libs
2011-09-28T11:38:38.396+03:30 [05000 verbose 'Default'] [ovfTool.cpp] Determining source
2011-09-28T11:38:38.396+03:30 [05000 verbose 'Default'] [ovfTool.cpp] Determining target
Opening OVA source: K:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram).ova

2011-09-28T11:38:38.490+03:30 [05000 verbose 'Default'] OVF Descriptor: <?xml version="1.0" encoding="UTF-8"?>
--> <!--Generated by VMware VirtualCenter Server, User: Administrator, UTC time: 2011-07-30T02:20:18.871093Z-->
--> <Envelope vmw:buildId="build-345043" xmlns="http://schemas.dmtf.org/ovf/envelope/1" xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common" xmlns:ovf="http:
//schemas.dmtf.org/ovf/envelope/1" xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware.com/schema/ovf" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-->   <References>
-->     <File ovf:href="Win_2008_X64_-Sharepoint_2_-_IP_65.122__200G_-8G(Ram)-disk1.vmdk" ovf:id="file1" ovf:size="30856148480" />
-->     <File ovf:href="Win_2008_X64_-Sharepoint_2_-_IP_65.122__200G_-8G(Ram)-file1.iso" ovf:id="file2" ovf:size="3735289856" />
-->   </References>
-->   <DiskSection>
-->     <Info>Virtual disk information</Info>
-->     <Disk ovf:capacity="200" ovf:capacityAllocationUnits="byte * 2^30" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces
/specifications/vmdk.html#streamOptimized" ovf:populatedSize="45460160512" />
-->   </DiskSection>
-->   <NetworkSection>
-->     <Info>The list of logical networks</Info>
-->     <Network ovf:name="LAN">
-->       <Description>The LAN network</Description>
-->     </Network>
-->   </NetworkSection>
-->   <VirtualSystem ovf:id="Win 2008 X64 -Sharepoint 2 - IP:65.122  200G -8G(Ram)">
-->     <Info>A virtual machine</Info>
-->     <Name>Win 2008 X64 -Sharepoint 2 - IP:65.122  200G -8G(Ram)</Name>
-->     <OperatingSystemSection ovf:id="1" vmw:osType="windows7Server64Guest">
-->       <Info>The kind of installed guest operating system</Info>
-->       <Description>Microsoft Windows Server 2008 R2 (64-bit)</Description>
-->     </OperatingSystemSection>
-->     <VirtualHardwareSection>
-->       <Info>Virtual hardware requirements</Info>
-->       <System>
-->         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
-->         <vssd:InstanceID>0</vssd:InstanceID>
-->         <vssd:VirtualSystemIdentifier>Win 2008 X64 -Sharepoint 2 - IP:65.122  200G -8G(Ram)</vssd:VirtualSystemIdentifier>
-->         <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>
-->       </System>
-->       <Item>
-->         <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>
-->         <rasd:Description>Number of Virtual CPUs</rasd:Description>
-->         <rasd:ElementName>4 virtual CPU(s)</rasd:ElementName>
-->         <rasd:InstanceID>1</rasd:InstanceID>
-->         <rasd:ResourceType>3</rasd:ResourceType>
-->         <rasd:VirtualQuantity>4</rasd:VirtualQuantity>
-->       </Item>
-->       <Item>
-->         <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
-->         <rasd:Description>Memory Size</rasd:Description>
-->         <rasd:ElementName>8192MB of memory</rasd:ElementName>
-->         <rasd:InstanceID>2</rasd:InstanceID>
-->         <rasd:ResourceType>4</rasd:ResourceType>
-->         <rasd:VirtualQuantity>8192</rasd:VirtualQuantity>
-->       </Item>
-->       <Item ovf:required="false">
-->         <rasd:Address>0</rasd:Address>
-->         <rasd:Description>USB Controller</rasd:Description>
-->         <rasd:ElementName>USB controller</rasd:ElementName>
-->         <rasd:InstanceID>3</rasd:InstanceID>
-->         <rasd:ResourceType>23</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:Address>0</rasd:Address>
-->         <rasd:Description>SCSI Controller</rasd:Description>
-->         <rasd:ElementName>SCSI controller 0</rasd:ElementName>
-->         <rasd:InstanceID>4</rasd:InstanceID>
-->         <rasd:ResourceSubType>lsilogicsas</rasd:ResourceSubType>
-->         <rasd:ResourceType>6</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:Address>1</rasd:Address>
-->         <rasd:Description>IDE Controller</rasd:Description>
-->         <rasd:ElementName>IDE 1</rasd:ElementName>
-->         <rasd:InstanceID>5</rasd:InstanceID>
-->         <rasd:ResourceType>5</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:Address>0</rasd:Address>
-->         <rasd:Description>IDE Controller</rasd:Description>
-->         <rasd:ElementName>IDE 0</rasd:ElementName>
-->         <rasd:InstanceID>6</rasd:InstanceID>
-->         <rasd:ResourceType>5</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>
-->         <rasd:ElementName>Hard disk 1</rasd:ElementName>
-->         <rasd:HostResource>ovf:/disk/vmdisk1</rasd:HostResource>
-->         <rasd:InstanceID>7</rasd:InstanceID>
-->         <rasd:Parent>4</rasd:Parent>
-->         <rasd:ResourceType>17</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>
-->         <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
-->         <rasd:ElementName>CD/DVD Drive 1</rasd:ElementName>
-->         <rasd:HostResource>ovf:/file/file2</rasd:HostResource>
-->         <rasd:InstanceID>8</rasd:InstanceID>
-->         <rasd:Parent>5</rasd:Parent>
-->         <rasd:ResourceType>15</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:AddressOnParent>7</rasd:AddressOnParent>
-->         <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
-->         <rasd:Connection>LAN</rasd:Connection>
-->         <rasd:Description>E1000 ethernet adapter on "LAN"</rasd:Description>

-->         <rasd:ElementName>Network adapter 1</rasd:ElementName>
-->         <rasd:InstanceID>9</rasd:InstanceID>
-->         <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
-->         <rasd:ResourceType>10</rasd:ResourceType>
-->       </Item>
-->       <Item ovf:required="false">
-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>
-->         <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
-->         <rasd:Description>Floppy Drive</rasd:Description>
-->         <rasd:ElementName>Floppy drive 1</rasd:ElementName>
-->         <rasd:InstanceID>10</rasd:InstanceID>
-->         <rasd:ResourceType>14</rasd:ResourceType>
-->       </Item>
-->     </VirtualHardwareSection>
-->   </VirtualSystem>
--> </Envelope>
Opening VMX target: k:\
2011-09-28T11:38:44.896+03:30 [05000 verbose 'Default'] Creating disk k:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram)\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram)-disk1.vmdk, 419430400 sectors, lsilogicWriting VMX file: k:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram)\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram).vmx
2011-09-28T11:38:46.802+03:30 [05000 verbose 'Default'] Using file size as progress measure Disk Transfer Failed Error: Invalid access to memory location.
2011-09-28T11:38:46.865+03:30 [05000 verbose 'Default'] Backtrace:
--> backtrace[00] rip 0175fd23 (no symbol)
--> backtrace[01] rip 0166eb5e (no symbol)
--> backtrace[02] rip 0166f801 (no symbol)
--> backtrace[03] rip 0162f99a (no symbol)
--> backtrace[04] rip 01626bc2 (no symbol)
--> backtrace[05] rip 0175f44b (no symbol)
--> backtrace[06] rip 01673622 (no symbol)
--> backtrace[07] rip 0176f018 (no symbol)
--> backtrace[08] rip 0041a76e (no symbol)
--> backtrace[09] rip 0047fb6a (no symbol)
--> backtrace[10] rip 00480c62 (no symbol)
--> backtrace[11] rip 0041e4d5 (no symbol)
--> backtrace[12] rip 0043de50 (no symbol)
--> backtrace[13] rip 00467136 (no symbol)
--> backtrace[14] rip 004674bd (no symbol)
--> backtrace[15] rip 00418474 (no symbol)
--> backtrace[16] rip 004186f4 (no symbol)
--> backtrace[17] rip 005e82ff (no symbol)
--> backtrace[18] rip 7c817067 (no symbol)
-->
2011-09-28T11:38:46.865+03:30 [05000 verbose 'Default'] Deleting file: k:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram)\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram)-disk1.vmdk
Deleting directory: k:\Win 2008 X64 -Sharepoint 2 - IP_65.122  200G -8G(Ram)
Completed with errors

*************************************************************************************************

Ps : i can't deploy my ova file with deploy OVF Template... in Esx and neither with ovatool !!
any idea ?

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.

I have a .ova created supplied to me that I'd like to open on several local copies of VMWare Workstation.

On one machine I am able to open it successfully.

On another using VMWare Workstation I get warnings that the .ova "did not pass OVF specification conformance or virtual hardware compliance checks" and then if I attempt to retry, I get an "Invalid access to memory location."

This is using VMWare Workstation 8.0.0 build-471780 on a Windows 7 Pro 64-bit 6.1.7601, SP 1 machine.

Attempting it with the latest build of OVFtool (2.1.0 build-461994) also fails.

Here's the output of ovftool.exe to the console - suggestions/ideas welcome!

Hi All,

Good Day to you.

OVF template deployment is taking lot of time to deploy new VM. Is there any way to upload OVF template on datastore and deploy vm from there.

Please need your support and suggestion.

Regards,

Baswaraj

Hello, I'm trying to export a VM as an OVA from an ESXi 4.0 host through our vCenter Server again version 4.0. At present my command looks like this:

ovftool.exe vi://<IP Address>/< Datacenter>/vm/<Folder Name>/<Folder Name>/<Folder Name> C:/<Path To OVA Store>/<VM Name.OVA>

The final folder name given above is the location of the VMX / VMDK files for the VM. I'm using version 2.1.0-467744-win-i386 of the ovftool from a Windows XP VM running SP3.

Issuing the above command appears to kick off the ova export process but it quickly dies and returns my prompt. The only output after issuing the command is a request for a username and password which I supply followed by the words "Opening VI source".

Any ideas where I'm going wrong?

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 have VMware Player 5.0.0. It internally has ovftool 3.0.1

I used VMware Studio2.0 to build an appliance in  OVA format  - It opened successfully by Player 5.0

Converted OVA -> OVF again from OVF->OVA using ovftool 3.0.1. (This is just for testing. Later I need to change OVF according to my need).

Now this re-generated OVA file is not supported by Player5.0. When I tried to open OVA file, Player failed with error 'Failed to open virtual machine: Failed to open OVF descriptor.'

Is this an issue with OVFTool or Player ? Please suggest.

BTW, I have used the below commands for convertion

Thanks in advance

--hemanth

Hi,

I am deploying a VM using a OVA format. The  size of OVA format is 60 GB. Currently free space on my datastore is 388 GB.

At the time of selecting Disk Format type if shows me in red that the disk size required is 1 TB therefore you cannot select THICK provisioning.

Therefore, i selected THIN provisiong. It THIN provisioing i am showed that Estimated Disk Usage is 112 GB which is less than the free space available.

But even after selecting THIN proviosing at the time of deployment it throws an error that it cannot create disk as the size of disk is larger than the maximum specified limit. 

My block size is of 1 MB.

Hi,

     I try to upload a physical server image to vcloud but it keep returning this error "Invalid response from Server"

The ovftool version is 3.01 and the vcloud is 1.5.

I have also attahed the ovf file.

Thank you.
Regards,

ET Goh

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,

HI,

I'm trying to create an OVF using ovftool 3.0.1. When I issue the ovftool command from the command line I get:

Error: cURL error: Couldn't connect to server
Completed with errors

I used the following command:

/usr/bin/ovftool vi://username:password@XX.XX.XX.XX/datacenter/vm/folder/vmname /destination

I can issue the command as above without the vmname to see if I can access Vsphere and to make sure I have a valid source locator.  The command is successful and returns a list of VMs I can use. When I add the VM name to the source locator path, I get the above error. The VM is pysically about 14GB in size (that is the space alloacted).

I can use the same command to another Vpshere server and I'm successful in creating the OVF. Which leads me to think that it might be a configuration issue with this Vsphere server?

What sorts of issues can lead to the above error?

Thanks,

Fernando

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 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.

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.

Can anyone help me out on "how to add additional Hard Disk and Ethernet Adapter for VM created in an ESXi server using ovftool.exe commandline.

We are working on a project that analyzes datacenter utilization and decides how to optimize VMs. We just released our VMware data collector. The data collectors continuously gets utilization data from your VMs and sends the data to our server. The data you provide will help improve our modeling and optimization engine. We only collect block box VM utilization metrics and we have no idea what is running in your datacenter. If you would like to participate, our data collector can be found here:

http://cloubrain.com/download.htm

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?