Hi All,
I am trying to convert vmdk file to ovf format using command line. I am using the below command:
# ovftool my_vm.vmdk new.ovf
Opening OVF source: my_vmdk.vmdk
Error: Failed to open OVF descriptor
Completed with errors
Not sure whats wrong in this command. Please help!
Thanks!
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:
The first step is to export your virtual machine from VirtualBox.
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">
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:
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>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
Hi,
I would like to convert VirtualBox 3.2.4 virtual machine to VMWare ESX 4.0.
In VirtualBox I have exported appliance to 0.9 format and then follow the following tutorial: http://www.ctrip.ufl.edu/howto-convert-virtualbox-to-vmware
When executing command "ovftool my.ovf my.vmx" I got the following error:
Opening OVF source: e:\VMW\my.ovf
Warning: No manifest file
Opening VMX target: e:\VMW\my.vmx
Error:
Line 39: Unsupported element 'Caption'
Line 40: Unsupported element 'Description'
Line 41: Unsupported element 'InstanceId'
Line 42: Unsupported element 'ResourceType'
Line 43: Unsupported element 'VirtualQuantity'
Line 37: Missing child element 'InstanceID'.
Line 37: Missing child element 'ResourceType'.
Line 48: Unsupported element 'Caption'
Line 49: Unsupported element 'Description'
Line 50: Unsupported element 'InstanceId'
Line 51: Unsupported element 'ResourceSubType'
Line 52: Unsupported element 'ResourceType'
Line 45: Missing child element 'InstanceID'.
Line 45: Missing child element 'ResourceType'.
Line 57: Unsupported element 'Caption'
Line 58: Unsupported element 'Description'
Line 59: Unsupported element 'InstanceId'
Line 60: Unsupported element 'ResourceSubType'
Line 61: Unsupported element 'ResourceType'
Line 54: Missing child element 'InstanceID'.
Line 54: Missing child element 'ResourceType'.
Line 65: Unsupported element 'Caption'
Line 66: Unsupported element 'Connection'
Line 67: Unsupported element 'InstanceId'
Line 68: Unsupported element 'ResourceSubType'
Line 69: Unsupported element 'ResourceType'
Line 63: Missing child element 'InstanceID'.
Line 63: Missing child element 'ResourceType'.
Line 74: Unsupported element 'Caption'
Line 75: Unsupported element 'Description'
Line 76: Unsupported element 'InstanceId'
Line 77: Unsupported element 'ResourceType'
Line 71: Missing child element 'InstanceID'.
Line 71: Missing child element 'ResourceType'.
Line 81: Unsupported element 'AutomaticAllocation'
Line 82: Unsupported element 'Caption'
Line 83: Unsupported element 'Description'
Line 84: Unsupported element 'InstanceId'
Line 85: Unsupported element 'ResourceSubType'
Line 86: Unsupported element 'ResourceType'
Line 79: Missing child element 'InstanceID'.
Line 79: Missing child element 'ResourceType'.
Line 90: Unsupported element 'Caption'
Line 91: Unsupported element 'Description'
Line 92: Unsupported element 'HostResource'
Line 93: Unsupported element 'InstanceId'
Line 94: Unsupported element 'Parent'
Line 95: Unsupported element 'ResourceType'
Line 88: Missing child element 'InstanceID'.
Line 88: Missing child element 'ResourceType'.
Line 99: Unsupported element 'AutomaticAllocation'
Line 100: Unsupported element 'Caption'
Line 101: Unsupported element 'Description'
Line 102: Unsupported element 'InstanceId'
Line 103: Unsupported element 'Parent'
Line 104: Unsupported element 'ResourceType'
Line 97: Missing child element 'InstanceID'.
Line 97: Missing child element 'ResourceType'.
Please see attached ovf file.
What should I do?
Thanks
I'm trying to use the ovftool to import a OVA file into a ESXi server. However I get the following error
Error: OVF Package is not supported by target:
- Line 118: Unsupported element 'Property'
Completed with errors
The related lines in the OVF file are:
<ProductSection ovf:class="vami" ovf:instance="*******">
<Info>Information about the installed software</Info>
<Category>Networking Properties</Category>
118--> <Property ovf:key="gateway" ovf:type="string" ovf:userConfigurable="true">
<Label>Default Gateway</Label>
<Description>The default gateway address for this VM. Leave blank if DHCP is desired.</Description>
</Property>
<Property ovf:key="DNS" ovf:type="string" ovf:userConfigurable="true">
Based on some initial investigation I have done I beleive this is because the ProductSection is defaulting to required="true" which forces ESXi to use these fields, however ESXi doesn't seem to support this and it errors out as shown above.
The OVA file was generated using ovftoolto export VM in a vcenter instance. This OVA file imports fine into vcenter, but not ESXi
Is there anyway to configure ovftoolwhen run against vcenter to generate required="false" in the ProductSection elements?
<ProductSection ovf:class="vami" ovf:instance="*******" ovf:required="false">
Or some otherway to get ovftoolto export a VM from vcenter as an OVA that will import into ESXi?
ovftool 2.1, ESXi 4.1, vCenter 4.1
I have a .iso image from which I want to create a .ova , But everytime I run into a problem
Error: Curl error: Couldn't connect to server
Completed with errors
Here is the command I used,
ovftool vi://user:master/@14.23.12.34:443/rt4/www/html/imgs/qweTER7.3/.tyRani/NEWCFT/CFT-NEW-5.23.23.iso /rt4/www/html/tmp_ova/CFT-NEW-5.23.23.ova
Not sure whats wrong with this command, I don't have special character in my password or username
please note that 14.23.12.34 is a linux machine and both source and target are in same machine and Im executing ovftool command in same linux machine.
Thank you
Mac
hi,
i'm very newbie on terminal and i get this error when i tried to convert ova file to vmx. It says completed with errors but I can't locate any file, anywhere, and also the whole process is to fast for OVF Tolls to do anything.
What am i missing? Thanks
Miguel
MCR:~ mcr$ /Applications/VMware\ OVF\ Tool/ovftool --lax /Users/mcr/Downloads/untitled\ folder/Ubuntu\ FEUP/Ubuntu\ FEUP.ova exploit.vmx
Opening OVA source: /Users/mcr/Downloads/untitled folder/Ubuntu FEUP/Ubuntu FEUP.ova
Opening VMX target: exploit.vmx
Error: OVF Package is not supported by target:
- Line 92: Unsupported element 'StorageItem'
- Line 101: Unsupported element 'StorageItem'
- Line 110: Unsupported element 'EthernetPortItem'
Completed with errors
I try to deploy a OVA into a vCenter 5.5, using OVFTool with the following command:
/usr/bin/ovftool --powerOn --acceptAllEulas --noSSLVerify --skipManifestCheck --allowAllExtraConfig --X:enableHiddenProperties --deploymentOption=${VMNAME_DEPLOYMENT_SIZE} "--net:Network 1=${VMNAME_PORTGROUP}" --datastore=${VMNAME_DATASTORE} --diskMode=${VMNAME_DISK_TYPE} --name=${VMNAME_DISPLAY_NAME} --prop:vami.DNS.APPLIANCE=${VMNAME_DNS} --prop:vami.gateway.APPLIANCE=${VMNAME_GATEWAY} --prop:vami.ip0.APPLIANCE=${VMNAME_IPADDRESS} --prop:vami.netmask0.APPLIANCE=${VMNAME_NETMASK} --prop:guestinfo.cis.appliance.ssh.enabled=${ENABLE_SSH} ${VMNAME_OVA} vi:/${VCENTER_USERNAME}:${VCENTER_PASSWORD}@${VCENTER_HOSTNAME}/?dns=${ESXI_HOSTNAME}
and I got this error:
Opening VMX target: vi:/administrator*************
Error: OVF Package is not supported by target:
- Line 768: Unsupported virtual hardware device 'VirtualSCSI'.
Warning:
- ExtraConfig options exists in source.
Completed with errors
The OVF file has the following settings:
<Item>
LINE768--> <rasd:Address xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">0</rasd:Address>
<rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">SCSI Controller 0 - pvscsi</rasd:ElementName>
<rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">4</rasd:InstanceID>
<rasd:ResourceSubType>virtualSCSI</rasd:ResourceSubType>
<rasd:ResourceType>6</rasd:ResourceType>
</Item>
and also :
<System>
<vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
<vssd:InstanceID>0</vssd:InstanceID>
<vssd:VirtualSystemType>vmx-07 vmx-08 vmx-09</vssd:VirtualSystemType>
</System>
Any advice on how to fix this issue and deploy the OVA?
Thanks.
I'm trying to create an OVA file from an installed VM. If I try creating it with ovftool 3.5, it downloads everything completely then gives me the following error:
SHA1 digest of file https://172.31.68.10:443/ha-nfc/52cca89a-6cde-c7a7-0810-25ff2197d3d6/disk-1.iso does not match manifest
and then deletes the file(s) it generated.
I am using compress=0 and --noImageFiles so i don't get the install iso.
If I manually go into Edit Settings and remove the cdrom, then 3.5 creates the ova correctly.
If I use ovftool 2.0, it succeeds even without manually removing the cdrom iso.
I've seen posts where users get the same error I do when they are going ova/f to vm and the answer is to delete the manifest. Since all of the files are deleted after the error message, I don't have the option to delete the locally created manifest.
Is there a way to keep the files around even after a manifest error?
Does anyone know why ovftool 3.5 would fail in this case and 2.0 would word? Has there been some deprecation between the two of them?
Thanks,
Mike
Hello
I installed ovftool on SLES 11 SP1 but when I try to use it....says Error: Locale Initialization Failed =(