Hi,

I have a ESXi 5.0 server running which has a Guest VM running CentOS 5.6.

The ESXi server is a standalone server, not included in a datacenter, not managed by vCenter.

The server has a HDD of 80G which has both the ESXi host & the Guest OS running on top of it.

I installed ovftools on my Windows laptop & tried to create a ovf from the VM but am unsuccessful. I constantly get the following error -

c:\>ovftool vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS c:\testVM.ovf

Error: Cannot parse locater: vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS

Completed with errors

The local datastore name is "datastore1"

Can someone help me out here with forming the correct the ovftool command to create an ovf & possibly an OVA out of the running VM?

Thanks

Bhushan Pathak

Hello all,

I am having an issue with deploying an OVF that was exported from VirtualBox. Made sure the steps were followed in this article:

http://www.ctrip.ufl.edu/howto-convert-virtualbox-to-vmware

In short...

- Export as 0.9 version OVF from VirtualBox

- Edit the OVF file and fix the sections noted in the link

- Run the VMWare ovftool [version 2.0.1] against it to convert to vmx or just import direct to ESX host

I die in step three of the list above.

ESX Import Attempt:

C:\PROGRA~1\VMware\VMWARE~2>ovftool.exe --lax -ds=DataStore_CLST01_OS_1 -nw="VLA
N 5 - Access" xxxxx-WUI-1.0.ovf vi://root:xxxxx@esx_server/
Opening OVF source: xxxxx-WUI-1.0.ovf
Warning: No manifest file
Opening VI target: vi://root@esx_server

Error: OVF Package is not supported by target:
- Line 44: Unsupported element 'Caption'

Convert to VMX Attempt:

C:\PROGRA~1\VMware\VMWARE~2>ovftool.exe --lax xxxxx-WUI-1.0.ovf xxxxx-WUI-1.0.
vmx
Opening OVF source: xxxxx-WUI-1.0.ovf
Warning: No manifest file
Opening VMX target: xxxxx-WUI-1.0.vmx
Error:
- Line 44: Unsupported element 'Caption'
- Line 45: Unsupported element 'Description'
- Line 46: Unsupported element 'InstanceId'
- Line 47: Unsupported element 'ResourceType'
- Line 48: Unsupported element 'VirtualQuantity'
- Line 42: Missing child element 'InstanceID'.
- Line 42: Missing child element 'ResourceType'.
- Line 53: Unsupported element 'Caption'
- Line 54: Unsupported element 'Description'
- Line 55: Unsupported element 'InstanceId'
- Line 56: Unsupported element 'ResourceSubType'
- Line 57: Unsupported element 'ResourceType'
- Line 50: Missing child element 'InstanceID'.
- Line 50: Missing child element 'ResourceType'.
- Line 62: Unsupported element 'Caption'
- Line 63: Unsupported element 'Description'
- Line 64: Unsupported element 'InstanceId'
- Line 65: Unsupported element 'ResourceSubType'
- Line 66: Unsupported element 'ResourceType'
- Line 59: Missing child element 'InstanceID'.
- Line 59: Missing child element 'ResourceType'.
- Line 71: Unsupported element 'Caption'
- Line 72: Unsupported element 'Description'
- Line 73: Unsupported element 'InstanceId'
- Line 74: Unsupported element 'ResourceSubType'
- Line 75: Unsupported element 'ResourceType'
- Line 68: Missing child element 'InstanceID'.
- Line 68: Missing child element 'ResourceType'.
- Line 79: Unsupported element 'Caption'
- Line 80: Unsupported element 'Connection'
- Line 81: Unsupported element 'InstanceId'
- Line 82: Unsupported element 'ResourceSubType'
- Line 83: Unsupported element 'ResourceType'
- Line 77: Missing child element 'InstanceID'.
- Line 77: Missing child element 'ResourceType'.
- Line 88: Unsupported element 'Caption'
- Line 89: Unsupported element 'Description'
- Line 90: Unsupported element 'InstanceId'
- Line 91: Unsupported element 'ResourceType'
- Line 85: Missing child element 'InstanceID'.
- Line 85: Missing child element 'ResourceType'.
- Line 96: Unsupported element 'Caption'
- Line 97: Unsupported element 'Description'
- Line 98: Unsupported element 'InstanceId'
- Line 99: Unsupported element 'ResourceType'
- Line 100: Unsupported element 'ResourceSubType'
- Line 93: Missing child element 'InstanceID'.
- Line 93: Missing child element 'ResourceType'.
- Line 104: Unsupported element 'AutomaticAllocation'
- Line 105: Unsupported element 'Caption'
- Line 106: Unsupported element 'Description'
- Line 107: Unsupported element 'InstanceId'
- Line 108: Unsupported element 'Parent'
- Line 109: Unsupported element 'ResourceType'
- Line 102: Missing child element 'InstanceID'.
- Line 102: Missing child element 'ResourceType'.
- Line 113: Unsupported element 'Caption'
- Line 114: Unsupported element 'Description'
- Line 115: Unsupported element 'HostResource'
- Line 116: Unsupported element 'InstanceId'
- Line 117: Unsupported element 'Parent'
- Line 118: Unsupported element 'ResourceType'
- Line 111: Missing child element 'InstanceID'.
- Line 111: Missing child element 'ResourceType'.

Any ideas?

Thanks in advance.

it is simple to export ONE vm in vsphere client to one OVA file (File ->Export->Export OVF template, and then select ova in dropbox). But is there a way to export multiple VM to ONE OVA files? Can use ovftool to do that?


 


Any comment or hint is highly appreciated!


 


Hobby

Stupid question

What is the difference between OVA and OVF; I've seen identical files with this 2 extensions.

Is it related with virtual hardware versions (OVA- VM 7, OVF- VM 4).

I have an OVF I'm trying to import into VI (ESX 3.5) and I'm getting the following error:

Error: OVF Package is not supported by target:
- Line 57: No space left for device '7' on parent controller '6'.

Here's the snippet of OVF:

      <Item>
        <rasd:Address>0</rasd:Address>
        <rasd:ElementName>IDE 0</rasd:ElementName>
        <rasd:InstanceID>6</rasd:InstanceID>
        <rasd:ResourceSubType>piix4</rasd:ResourceSubType>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>Harddisk disk1</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/disk1</rasd:HostResource>
        <rasd:InstanceID>7</rasd:InstanceID>
        <rasd:Parent>6</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:Address>1</rasd:Address>
        <rasd:ElementName>IDE 1</rasd:ElementName>
        <rasd:InstanceID>8</rasd:InstanceID>
        <rasd:ResourceSubType>piix4</rasd:ResourceSubType>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>

Thanks!

Mike

Hi All,

Please help me as I am trying to deploy my OVF in an esxi and I get the following error

"Failed to deploy OVF package: File ds:///vmfs/volumes/546b400f-680d4bc0-11f7-001517d3b60c/_deviceImage-0.iso was not found"

I don't know if I am correct if i deduce that the export might have an iso image mounted on it and now it can't locate it?

I exported the OVF from esxi 5.5 and the destination esxi is also 5.5.

I have also attached the screenshot of the error mentioned above.

Please help

Appreciate all the help I could get and thank you in advance

Regards,

Hi,

Using ESXi 6.0.0, ovftool 4.2

I am trying to export a VM in a standalone ESXi to OVF using the following sintaxys:

C:\Program Files\VMware\VMware OVF Tool>ovftool "vi://root:pass@esxiip/ha-datacenter?ds=\[SSD Datastore\] nubodb_gima/nubodb.vmx" c:\nubodb-ovf\

But it is showing: Error: Locator does not refer to an object: vi://root@esxiip/ha-datacenter?ds=\[SSD%20Datastore\]%20nubodb_gima/nubodb.vmx

VM is located in:  [SSD Datastore] nubodb_gima/nubodb.vmx

I looked at the documentation and also the examples provided by ovftool but it is not working. I'll apreciate any help.

Gracias,

From virtualmachine i have exported .ovf file from the following website http://www.techrepublic.com/blog/windows-and-office/how-do-i-convert-virtualbox-files-to-work-with-vmware-workstation/#.

and i recieved the following error in cmd prompt.

can anyone please help me to understand error line 84 and prove me solution .

........................................................................................

Error:

- Line 84: Could not parse the document: 'mismatched tag'

Warning:

- No manifest file found.

Completed with errors.

---------------------------------------------------------------------------------------

Steps followed:

Step 1: Export your virtual machine

The first step is to export your virtual machine from VirtualBox.

Step 2: Editing your .ovf file

The file you need to edit will be the .ovf file that serves as the descriptor for your virtual machine. You MUST open this in a text editor. Do NOT open it in a word processor as this will add extra characters to the file, which will render it unreadable by either VirtualBox or VMWare. The first section you need to edit is the format section. Look for a line of code (near the top) that contains this phrase:

ovf:format=

What follows that section needs to be changed to:

"http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"

The next edit (in the same file) is the Virtual SystemType, and it must be one of the following:

<vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType> (for a esx 4.0)

<vssd:VirtualSystemType>vmx-04</vssd:VirtualSystemType> (for esx 3.5.x and 4.0 hosts)

Believe it or not, the next item to edit is the rsad for the sound card. The section will look similar to:

<Item>

<rasd:Caption>sound</rasd:Caption>

<rasd:Description>Sound Card</rasd:Description>

<rasd:InstanceId>6</rasd:InstanceId>

<rasd:ResourceType>35</rasd:ResourceType>

<rasd:ResourceSubType>ensoniq1371</rasd:ResourceSubType>

<rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>

<rasd:AddressOnParent>3</rasd:AddressOnParent>

</Item>

To the above section, add the following after the first <Item> tag:

<Item ovf:required="false">

Step 3: Using the OVF tool

This step requires you to download and install the VMWare OVF Tool (you will have to log in first). The OVF tool is command-line only, and it will convert your newly prepped .ovf file into a .vmx that VMWare can use. To do this, follow these steps:

• Click Start | Run.
• Type cmd.
• In the command window, change to the directory you installed the OVF Tool into and then issue the command:ovftool appliance.ovf new_appliance.vmx(Where appliance.ovf is the name of the appliance you exported from VirtualBox and new_appliance.vmx is the name you want to give the new virtual appliance. Depending on the size of your virtual appliance, this could take a while.)

How to reduce the size of OVF file?

I am very new to OVF template feature and I created an OVF file from windows 7 VM. I created this OVF file from vSphere client (5.1) by using the export template option.

But the size the OVF file is very huge around 12 GB, but only 2GB of space is occupied by installed third party software in that VM. Not sure why OVF file is showing very huge size.

This VM have the configuration with HDD – 80GB (Thin provisioning), RAM – 20 GB and 4 vCPUs. VM belong to the ESX also having another 50 VMs with different configuration. One observation, Windows create a pagefile equal to RAM size in C:\ of the VM, so the overall utilized disk is showing as 40+ GB before export.

I used ovftool with “–compress=9” option, but still it reduced only 1 GB space, also tried with tried different option including acceptAllEulas and chunkSize, but overall size didn’t reduce.

Is there any way to reduce the vmdk file size to less than 5GB?

Hello All,

Can anybody please help me with the VMware OVF Tool command line utility ?

It is supposed to allow you to import and export Virtual Machines containers (VMX files).

How do we specify the path to the .VMX we want to export from an ESXi server ?

The command line option <source locator> asks for a "vSphere locator identifying a virtual machine or vApp on vCenter, ESXi, or VMware Server" but I just can't make the application recognize any thing I try.

For example, on the following command line option:

> ovftool vi://username:pass@my_host/my_datacenter/vm/my_vm_folder/my_vm_name

What does "my_datacenter" is supposed to mean ? Where do I find the name of my vSphere ESXi server ?

I've installed the OVT Tool at the vSphere server itself. The binary is working well at Linux ESXi shell. I just don't understand how to point it to the specific file I want to export at the datastore.

[root@localhost:~] uname -a

VMkernel localhost 6.0.0 #1 SMP Release build-3620759 Mar  3 2016 18:41:52 x86_64 x86_64 x86_64 ESXi

[root@localhost:~] ls -al vmfs/volumes/datastore1/cancao-cead/

total 174242840

drwxr-xr-x    1 root     root          2520 Nov 21 11:14 .

drwxr-xr-t    1 root     root          2240 Oct 26 19:56 ..

-rw-------    1 root     root     17179869184 Nov 21 11:14 cancao-cead-ab4b36ea.vswp

-rw-------    1 root     root     161061273600 Nov 22 18:44 cancao-cead-flat.vmdk

-rw-------    1 root     root          8684 Nov 22 18:37 cancao-cead.nvram

-rw-------    1 root     root           475 Nov 21 11:14 cancao-cead.vmdk

-rw-r--r--    1 root     root             0 May 28  2016 cancao-cead.vmsd

-rwxr-xr-x    1 root     root          2740 Nov 21 11:14 cancao-cead.vmx

The file I'm trying to reach from the OVF Tool command line is last one:cancao-cead.vmx

How can I make OVF Tool command to find that file ?

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!

I have tried everything and having trouble with this command and here is the error I am getting.  I have tried "--network=VM Network" and every option I can think of and those options seems correct because the command does execute, but I get the same results.  The thing is I do not currently need a network adapter installed on this machine after I bring it into the VMWare environment

C:\Program Files\VMware\VMware OVF Tool&gt;ovftool.exe --datastore=EVA1Disk1 --net work="Host Only" c:\Temp\Netscaler\NSVPX-ESX-9.1-101.5.ovf vi://root@128.1.60.200

Opening OVF source: c:\Temp\Netscaler\NSVPX-ESX-9.1-101.5.ovf Please enter login information for target vi://128.1.60.200/ Username: root Password: ********* Opening VI target: vi://root@128.1.60.200/Error: No network mapping specified OVF networks:  NS_NIC_1_1  VM Network Target networks:  Host Only  VM Network

What is the difference between OVF 1.0 and 0.9 version? I would be interested in knowing about the major enchancements made in the newer versions and thereby the advantages of the same.

Thanks in advance

Hello, I'm having some trouble getting both the vSphere Client and ovftool to

import my OVF's.  When using the vSphere Client, I successfully walk through

the wizard to "Deploy OVF Template", I click Finish on the final wizard screen

and progress dialog pops up.  It counts up to 100% complete while showing

"Deploying disk 1 of 1..." and then always fails with the following error

displayed on a popup window:

"Failed to deploy OVF package: The remote server returned an error: (500)

Internal Server Error"

I then tried using ovftool, to convert my OVF to VMX format.  Similarly, the

"Disk Progress" percentage counts up to 100% and then errors with:

Opening OVF source: stout-1-x86_64.ovf

Warning: No manifest file

Opening VMX target: stout-out/

Target: stout-out/stout-1-x86_64/stout-1-x86_64.vmx

Disk Transfer Failed           

Error: Failed to open source disk: stout-1-x86_64.vmdk

In both cases, it seems the problem is with my disk file, which is a

stream optimized VMDK.  Just to check, I verified that I was able to import

this exact same disk file built into an OVF 0.9 using Virtual Infrastructure

Client 2.5.0.  So, I'm at a loss as to what the problem may be.  Do you have

to build the stream optimized vmdk any differently?  Any other suggestions on

how I may be able to debug this further?

Thanks for any help,

James Slagle

Hello

I installed ovftool on SLES 11 SP1 but when I try to use it....says Error: Locale Initialization Failed =(

i am using ovftool (verisn 2.01), and i have got some error  as below, anyone ever met these? SOS

(1)

command:"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --X:logToConsole "e:\shared\Windowns2003EServerSp2\Win2003.vmx" "e:\shared\1\Win2003_0.vof"

error information:

[2011-03-08 14:51:19.640 03480 verbose 'ovftool'] Subscribing to signal: 2 (SIGINT)

[2011-03-08 14:51:19.640 03480 verbose 'ovftool'] Subscribing to signal: 4 (SIGILL)

[2011-03-08 14:51:19.640 03480 verbose 'ovftool'] Subscribing to signal: 22 (SIGABRT)

[2011-03-08 14:51:19.640 03480 verbose 'ovftool'] Subscribing to signal: 8 (SIGFPE)

[2011-03-08 14:51:19.640 03480 verbose 'ovftool'] Subscribing to signal: 15 (SIGTERM)

[2011-03-08 14:51:19.640 03480 verbose 'ovftool'] [ovfTool.cpp] Using home directory C:\Documents and Settings\tom\Application Data\VMware\ovftool.cfg

[2011-03-08 14:51:19.640 03480 verbose 'ovftool'] [ovfTool.cpp] OvfTool Environment:

/X:fencedMode = "bridged"

/X:imageReadSize = "262144"

/X:logToConsole = "true"

/X:maxNumberOfTermSignals = "5"

/X:maxRedirects = "256"

/X:maximalDeltaConfSize = "8"

/X:maximalDeltaTreeSize = "6"

/X:progressSmoothing = "60"

/X:vimSessionTimeout = "600"

/authdPortSource = "902"

/authdPortTarget = "902"

/prgPath = "C:\Program Files\VMware\VMware OVF Tool"

/source = "e:\shared\Windowns2003EServerSp2\Win2003.vmx"

/target = "e:\shared\1\Win2003_0.vof"

[2011-03-08 14:51:19.656 03480 verbose 'ovftool'] [ovfTool.cpp] Done initializing libs

[2011-03-08 14:51:19.656 03480 verbose 'ovftool'] [ovfTool.cpp] Determining source

[2011-03-08 14:51:19.671 03480 verbose 'ovftool'] [ovfTool.cpp] Determining target

Opening VMX source: e:\shared\Windowns2003EServerSp2\Win2003.vmx

[2011-03-08 14:51:19.750 03480 error 'ovftool'] CoreDump: ExternalCoreMaster was not setup

[2011-03-08 14:51:19.750 03480 error 'ovftool'] CoreDump: ExternalCoreMaster was not setup

[2011-03-08 14:51:19.765 03480 info 'ovftool'] CoreDump: Writing minidump

[2011-03-08 14:51:19.843 03480 panic 'ovftool']

Panic: Win32 exception: Access Violation (0xc0000005)

   Read (0) at address 00000000

   rip: 7855b9f0 rsp: 0012fb14 rbp: 0012fb20

   rax: 00000000 rbx: 0012fc78 rcx: 00000000

   rdx: 00000004 rdi: 029a3d38 rsi: 0012fc78

Backtrace:

backtrace[00] rip 01b9936d (no symbol)

backtrace[01] rip 01b06fa4 (no symbol)

backtrace[02] rip 01b07517 (no symbol)

backtrace[03] rip 01bb2d49 (no symbol)

backtrace[04] rip 01bb2e6d (no symbol)

backtrace[05] rip 01ba72f4 (no symbol)

backtrace[06] rip 7857dca0 (no symbol)

backtrace[07] rip 7857d4eb (no symbol)

backtrace[08] rip 7857d8b6 (no symbol)

backtrace[09] rip 7857d9d3 (no symbol)

backtrace[10] rip 7857db8a (no symbol)

backtrace[11] rip 7c9232a8 (no symbol)

backtrace[12] rip 7c92327a (no symbol)

backtrace[13] rip 7c92e48a (no symbol)

backtrace[14] rip 78487155 (no symbol)

backtrace[15] rip 0044661f (no symbol)

backtrace[16] rip 0044aedf (no symbol)

backtrace[17] rip 0040cfba (no symbol)

backtrace[18] rip 0058799b (no symbol)

backtrace[19] rip 7c817077 (no symbol)

Section for VMware Workstation, pid=3292, version=e.x.p, build=build-260188, option=Release

[2011-03-08 14:51:19.843 03480 panic 'ovftool'] Win32 exception: Access Violation (0xc0000005)

   Read (0) at address 00000000

   rip: 7855b9f0 rsp: 0012fb14 rbp: 0012fb20

   rax: 00000000 rbx: 0012fc78 rcx: 00000000

   rdx: 00000004 rdi: 029a3d38 rsi: 0012fc78

(2)

command:"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --X:logToConsole "e:\shared\Windows2003EESp2\Clone of Windows Server 2003 Enterprise Edition.vmx" "e:\shared\1\Clone of Windows Server 2003 Enterprise Edition_0.vof"

error information:

[2011-03-08 14:51:21.281 01468 verbose 'ovftool'] Subscribing to signal: 2 (SIGINT)

[2011-03-08 14:51:21.281 01468 verbose 'ovftool'] Subscribing to signal: 4 (SIGILL)

[2011-03-08 14:51:21.281 01468 verbose 'ovftool'] Subscribing to signal: 22 (SIGABRT)

[2011-03-08 14:51:21.281 01468 verbose 'ovftool'] Subscribing to signal: 8 (SIGFPE)

[2011-03-08 14:51:21.281 01468 verbose 'ovftool'] Subscribing to signal: 15 (SIGTERM)

[2011-03-08 14:51:21.281 01468 verbose 'ovftool'] [ovfTool.cpp] Using home directory C:\Documents and Settings\tom\Application Data\VMware\ovftool.cfg

[2011-03-08 14:51:21.281 01468 verbose 'ovftool'] [ovfTool.cpp] OvfTool Environment:
/X:fencedMode = "bridged"
/X:imageReadSize = "262144"
/X:logToConsole = "true"
/X:maxNumberOfTermSignals = "5"
/X:maxRedirects = "256"
/X:maximalDeltaConfSize = "8"
/X:maximalDeltaTreeSize = "6"
/X:progressSmoothing = "60"
/X:vimSessionTimeout = "600"
/authdPortSource = "902"
/authdPortTarget = "902"
/prgPath = "C:\Program Files\VMware\VMware OVF Tool"
/source = "e:\shared\Windows2003EESp2\Clone of Windows Server 2003 Enterprise Edition.vmx"
/target = "e:\shared\1\Clone of Windows Server 2003 Enterprise Edition_0.vof"

[2011-03-08 14:51:21.296 01468 verbose 'ovftool'] [ovfTool.cpp] Done initializing libs

[2011-03-08 14:51:21.296 01468 verbose 'ovftool'] [ovfTool.cpp] Determining source

[2011-03-08 14:51:21.296 01468 verbose 'ovftool'] [ovfTool.cpp] Determining target

Opening VMX source: e:\shared\Windows2003EESp2\Clone of Windows Server 2003 Enterprise Edition.vmx
[2011-03-08 14:51:21.359 01468 verbose 'ovftool'] OVF Descriptor: <?xml version="1.0" encoding="UTF-8"?>
<!--Generated by VMware ovftool 2.0.1 (build-260188), UTC time: 2011-03-08T06:51:21.359375Z-->
<Envelope vmw:buildId="build-260188" 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="e%3a%5cshared%5cWindows2003EESp2%5cWindows%20Server%202003%20Enterprise%20Edition-cl1-000005.vmdk" ovf:id="file1"/>
  </References>
  <DiskSection>
    <Info>Virtual disk information</Info>
    <Disk ovf:capacity="8" ovf:capacityAllocationUnits="byte * 2^30" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"/>
  </DiskSection>
  <NetworkSection>
    <Info>The list of logical networks</Info>
    <Network ovf:name="bridged">
      <Description>The bridged network</Description>
    </Network>
  </NetworkSection>
  <VirtualSystem ovf:id="vm">
    <Info>A virtual machine</Info>
    <Name>Win 2003SP2 Vulnerrability</Name>
    <OperatingSystemSection ovf:id="69" vmw:osType="winNetEnterpriseGuest">
      <Info>The kind of installed guest operating system</Info>
    </OperatingSystemSection>
    <VirtualHardwareSection>
      <Info>Virtual hardware requirements</Info>
      <System>
        <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
        <vssd:InstanceID>0</vssd:InstanceID>
        <vssd:VirtualSystemIdentifier>Win 2003SP2 Vulnerrability</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>1 virtual CPU(s)</rasd:ElementName>
        <rasd:InstanceID>1</rasd:InstanceID>
        <rasd:ResourceType>3</rasd:ResourceType>
        <rasd:VirtualQuantity>1</rasd:VirtualQuantity>
      </Item>
      <Item>
        <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
        <rasd:Description>Memory Size</rasd:Description>
        <rasd:ElementName>384MB of memory</rasd:ElementName>
        <rasd:InstanceID>2</rasd:InstanceID>
        <rasd:ResourceType>4</rasd:ResourceType>
        <rasd:VirtualQuantity>384</rasd:VirtualQuantity>
      </Item>
      <Item ovf:required="false">
        <rasd:Address>0</rasd:Address>
        <rasd:Description>USB Controller</rasd:Description>
        <rasd:ElementName>usb</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>scsiController0</rasd:ElementName>
        <rasd:InstanceID>4</rasd:InstanceID>
        <rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
        <rasd:ResourceType>6</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:Address>1</rasd:Address>
        <rasd:Description>IDE Controller</rasd:Description>
        <rasd:ElementName>ideController1</rasd:ElementName>
        <rasd:InstanceID>5</rasd:InstanceID>
        <rasd:ResourceType>5</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>floppy0</rasd:ElementName>
        <rasd:InstanceID>6</rasd:InstanceID>
        <rasd:ResourceType>14</rasd:ResourceType>
      </Item>
      <Item ovf:required="false">
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
        <rasd:ElementName>cdrom1</rasd:ElementName>
        <rasd:InstanceID>7</rasd:InstanceID>
        <rasd:Parent>5</rasd:Parent>
        <rasd:ResourceType>15</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>disk1</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/vmdisk1</rasd:HostResource>
        <rasd:InstanceID>8</rasd:InstanceID>
        <rasd:Parent>4</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>2</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>bridged</rasd:Connection>
        <rasd:Description>E1000 ethernet adapter on &quot;bridged&quot;</rasd:Description>
        <rasd:ElementName>ethernet0</rasd:ElementName>
        <rasd:InstanceID>9</rasd:InstanceID>
        <rasd:ResourceSubType>E1000</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
      </Item>
    </VirtualHardwareSection>
    <AnnotationSection ovf:required="false">
      <Info>A human-readable annotation</Info>
      <Annotation>445端口漏洞服务，未做任何服务安装和修改。

Windows2003 企业版 sp2</Annotation>
    </AnnotationSection>
  </VirtualSystem>
</Envelope>

Opening OVF target: e:\shared\1\Clone of Windows Server 2003 Enterprise Edition_0.vof
Error:

- Line 106: Could not parse the document: 'not well-formed (invalid token)'.

I think that ofvtool is a great tool to move VM between ESXi and ESX servers.

I need to convert a VM with several snapshots, and I would like to keep them: how can I tell ovftool to keep snapshots while coreting the .ovf or .ova files?

When importing it I want to see all my snapshots.

Regards

marius

I need to write a script to remotely shotdown a guest VM, export it to .ova format an restart it.

Is there any sample I can start from?

Regards

marius

Hi,

I currently am trying to deploy an ovf onto an esxi machine. The ovf is currently located on the destination esxi machine.

Here is the command I was trying to use:

.\ovftool "https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1" vi://user:password@<ip address>

group1/Win7-5/Win7-5.ovf is the is the location of the ovf within the datastore.

When I try to execute this it has the error:

Error: Could not open URL https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1 (response code 404)

If i open up the vsphere UI and go through the deploy ovf wizard using

https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1  (same as above)

as the location of the ovf file it works fine.

If anyone can help me i would greatly appriciate it. I searched all over and couldnt find an answer anywhere else and couldnt figure it out when looking at the docs. Sorry if this is a repeat post.

Ray

Hi,

I am trying to deploy OVA using ovftool. I see the option --network and --net available for selecting the network by name, though I was not able to find a way to assign a static IP in the ovftool command itself. Something like --ip0=10.10.10.10. Is there a way we can do this? From UI when we deploy an OVA, we have provision to provide IP, Gateway, Netmask and DNS.

Thanks