hello, I am stuck.  Any help is much appreciated.

I am simply trying to export an OVF template from a vm (.vmx) in vCenter 4.1.0 using the OVF Tool.

The vm is located here:

<vcenter>/<datacenter>/vm/Build Server/sles11-sp1-x8664/yoshi

I can probe the object like this:

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi

OVF version:   1.0

VirtualApp:    false

Name:          yoshi

Download Size:     Unknown

Deployment Sizes:

  Flat disks:     80.00 GB

  Sparse disks:   Unknown

Networks:

  Name:        CVO VM Network

  Description: The CVO VM Network network

Virtual Hardware:

  Family:       vmx-07

  Disk Types:   SCSI-lsilogic

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/templates/ovf-templates/yoshi.ovf

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Error: Locator does not refer to an object: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/templates/ovf-templates/yoshi.ovf

Completed with errors

Can someone help identify the correct target locator?

I have also tried the following host path:

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/host/R\&D

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Opening VI target: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/host/R&D

Error: No target datastore specified. Possible completions:

  DespinaLS

  DevVMs

  NFS Install

  VM template backup

  dominator-nfs-install

  nfs-ds1

  puffinSanMedia

  skillet-ds1

  skillet-ds2

Completed with errors

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/host/R\&D/skillet-ds2

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Error: Locator does not refer to an object: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/host/R&D/skillet-ds2

Completed with errors

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/host/R\&D?ds=[skillet-ds2]

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Error: Datacenter object not found

Completed with errors

Hello all,

I am having a problem with the ovftool.

Here's what i did.

1)I created a VM running CentOS.

2)These are the 3 files that i got.

Test.vmx

Test.vmdk (Descriptor File)

# Disk DescriptorFile

version=1

CID=5046e880

parentCID=ffffffff

createType="vmfsPreallocated"

# Extent description

RW 83886080 VMFS "Test-flat.vmdk" 0

# The Disk Data Base

#DDB

ddb.virtualHWVersion = "4"

ddb.geometry.cylinders = "83220"

ddb.geometry.heads = "16"

ddb.geometry.sectors = "63"

ddb.adapterType = "lsilogic"

Test-flat.vmdk

3) This is the command that i ran

ovftool "Test.vmx" "Test_New.ova"

Please help!

Thank you

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

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

Hopefully this is the right place to ask this.

We have a product that's distributed as an OVA and have done so for years. We're finally getting around to supporting vSphere 6.5 but are running into an issue. If we deploy the OVA directly to a 6.5 host, the import works fine. However if we deploy via vCenter, it fails with the following error:

Failed to deploy OVF package.

Cause:

A general system error occurred:

An error occurred: Could not convert field 'spec' of structure 'com.vmware.vcenter.vdcs.floppy_model'

This only happens on vSphere 6.5. It works fine with vSphere 6.0 and earlier. When we create the template, we do have a floppy device (it's needed as we do our OS install during the build process) so I changed it so right before it creates the OVA using ovftool 4.1, I edit the vmx (while the vm is powered off) and remove all references to the floppy device. However the corresponding ovf file still has references to the floppy.

Any ideas what's going on and how to fix? I'm not sure why all of a sudden it stopped working in 6.5. From our end, the build process hasn't changes in years. I can attach the vmx and ovf files if that helps. Thanks!

Hi Guys,

Some quick background:
For the past two years I have used a deployment USB I created that consisted of a ks.cfg file that deployed Esxi, mcopy'd the OVA images to the local datastore and then finally used ovftools to deploy the OVA images

All source code and the USB has stayed the same through the years, with only minor changes to the Esxi version. But that has never caused an issue.
However I am trying this with Esxi 6.7 this time and I am getting curl SSL errors. Here is the log verbose log file:

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 4 (SIGILL)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 6 (SIGABRT)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 8 (SIGFPE)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 15 (SIGTERM)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 1 (SIGHUP)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 3 (SIGQUIT)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 5 (SIGTRAP)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 9 (SIGKILL)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Subscribing to signal: 13 (SIGPIPE)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Initializing progress

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] OvfTool Version: VMware ovftool 4.1.0 (build-2459827)

2018-07-16T14:31:04.824Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Using home directory: ./.ovftool

2018-07-16T14:31:04.832Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Curl Version: 7.30.0

2018-07-16T14:31:04.832Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Done initializing libs

2018-07-16T14:31:04.832Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Determining source

2018-07-16T14:31:04.833Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Determining target

2018-07-16T14:31:04.833Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Getting source

2018-07-16T14:31:04.833Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Parsing URL

2018-07-16T14:31:04.835Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Parsing URL

2018-07-16T14:31:04.838Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Opening source

2018-07-16T14:31:04.838Z verbose -[8922A00FC0] [Originator@6876 sub=Default] OvfPackageSourceBase::Open

2018-07-16T14:31:04.846Z verbose -[8922A00FC0] [Originator@6876 sub=Default] OvfPackageSourceBase parsing message bundle

2018-07-16T14:31:04.848Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Validating files

2018-07-16T14:31:04.848Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Getting target

2018-07-16T14:31:04.848Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Connecting to vi host

2018-07-16T14:31:04.848Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Skip SSL verification

2018-07-16T14:31:04.850Z verbose -[8922A00FC0] [Originator@6876 sub=HttpConnectionPool-000000] HttpConnectionPoolImpl created. maxPoolConnections = 20; idleTimeout = 900000000; maxOpenConnections = 20; maxConnectionAge = 0

2018-07-16T14:31:04.851Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Getting version of the VI host : 127.0.0.1

2018-07-16T14:31:04.851Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Initializing new curl session

2018-07-16T14:31:04.867Z verbose -[8922A00FC0] [Originator@6876 sub=Default] WebRequest set basic http authorization, username : root

2018-07-16T14:31:04.867Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Getting http page: https://127.0.0.1/sdk/vimServiceVersions.xml

2018-07-16T14:31:04.885Z verbose -[8922CF8700] [Originator@6876 sub=Default] Curl_perform error code 35 (SSL connect error)

2018-07-16T14:31:04.885Z verbose -[8922A00FC0] [Originator@6876 sub=Default] CURL error buffer: Unknown SSL protocol error in connection to 127.0.0.1:443

2018-07-16T14:31:04.890Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Curl session torn down

2018-07-16T14:31:04.892Z verbose -[8922A00FC0] [Originator@6876 sub=Default] Backtrace:

-->

--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-2459827, tag: -

--> backtrace[00] libvmacore.so[0x003D9C74]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)

--> backtrace[01] libvmacore.so[0x001DBF37]: Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)

--> backtrace[02] libvmacore.so[0x0018481D]: Vmacore::Throwable::Throwable(std::string const&)

--> backtrace[03] ovftool.bin[0x0020DFB3]

--> backtrace[04] ovftool.bin[0x00248E5D]

--> backtrace[05] ovftool.bin[0x0024C5C9]

--> backtrace[06] ovftool.bin[0x00295BC4]

--> backtrace[07] ovftool.bin[0x0029714C]

--> backtrace[08] ovftool.bin[0x00298991]

--> backtrace[09] ovftool.bin[0x001EC853]

--> backtrace[10] ovftool.bin[0x001EEB04]

--> backtrace[11] libc.so.6[0x0002192D]

--> backtrace[12] ovftool.bin[0x001626B9]

--> [backtrace end]

-->

I can see the error is because their is no SSL on  https://127.0.0.1/sdk/vimServiceVersions.xml - however there has never been. So why is it only complaining now?
An note I place the --noSSLVerify flag when using OVF tools. So you would this would be ignored.

Also for refrence here is the command I am using:

/vmfs/volumes/datastore1/vmware-ovftool/ovftool --X:logFile=ovf.log --X:logLevel=verbose --noSSLVerify -dm=thin --acceptAllEulas /vmfs/volumes/datastore1/VM.ova "vi://root:PASSWORD@127.0.0.1"

I am trying to install ovftool 4.1.0 on a Ubuntu guest I have on my Windows host.  I downloadedd the ovftool bundle changed permission to +x, started the bundle, and accepted the license.  It says it is ready to install and I press enter.  Then I get the below and ovftool is never installed.


 


Rolling back VMware installer component 2.1.0


Removing files..


Uninstalling VMware installer component 2.1.0


Deconfiguring...


 


Any ideas? The bundle I have is the 'VMware-ovftool-4.1.0-2459827-lin.x86_64.bundle' on Ubuntu 14


 

hello.

         I create a ova file from my ESXi 5.0.0 with ovftool 2.1.0-467744, then I deploy this ova file into ESXi 5.0.0 is success and work well.

But I can't deploy the same ova file into VMWare Player with ovftool 2.1.0-467744 installed. Why?

         Anybody has any idea? Thanks.

Best Regards,

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

Anyone using OVF extensively?

Environment...

ESXi 4 box, with a single very simple VM, just a VM, no disks, nothing more than a VM shell really.

ESXi 3.5 U 4 running a single VM, which has vCenter 4 running in it.  Windows 2008, 32, 1.5GB RAM for VM

Windows XP SP3 fully patched desktop to run OVF CLI tool for Windows and VIClient 4

Attempted...

1) From VI client, try to use GUI to Export OVF Template, VirtualCenter Service stops.

2) From Windows XP SP3 full patched desktop, where Windows OVF1.0 Tool installed, Attempt to do OVF export as attempted above, generates an unexpected exception trap.  vCenter 4 VMware Virtual Center server stops.

C:\Program Files\VMware\VMware OVF Tool&gt;ovftool "vi://administrator@192.168.15.3/Home Office/vm/Test01" ./Test01.OVF

Please enter login information for source vi://192.168.15.3/

Username: administrator

Password: *********

Opening VI source: vi://administrator@192.168.15.3/Home Office/vm/Test01

Error: The specified network name is no longer available.

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

Terminate process signal received - aborting operation

C:\Program Files\VMware\VMware OVF Tool&gt;

I'm trying to convert an VirtualBox OVF that we had prepared to use in a ESX environment, but am recieving errors.  First off, I just want to make sure we are able to do this and secondly if anyone is able to help me resolve the errors.

Initiall I received the following errors.  This is trying to do a conversion directly on the ovf I was given.

E:\Documents and Settings\user\Desktop&gt;ovftool debian-server-32bit.ovf debian-s
erver-32bit.vmx
Opening OVF source: debian-server-32bit.ovf
Warning: No manifest file
Opening VMX target: debian-server-32bit.vmx
Error:
- Line 8: Unsupported value 'http://www.vmware.com/specifications/vmdk.html#spa
rse' for attribute 'format' on element 'Disk'.
- Line 37: Unsupported element 'Description'
- Line 45: Unsupported element 'Description'
- Line 48: Unsupported element 'AllocationUnits'
- Line 54: Unsupported element 'Description'
- Line 57: Unsupported element 'ResourceSubType'
- Line 58: Unsupported element 'Address'
- Line 63: Unsupported element 'Description'
- Line 66: Unsupported element 'AutomaticAllocation'
- Line 67: Unsupported element 'AddressOnParent'
- Line 74: Unsupported element 'ResourceSubType'
- Line 75: Unsupported element 'AutomaticAllocation'
- Line 76: Unsupported element 'Connection'
- Line 81: Unsupported element 'Description'
- Line 84: Unsupported element 'Address'
- Line 89: Unsupported element 'Description'
- Line 92: Unsupported element 'ResourceSubType'
- Line 93: Unsupported element 'AutomaticAllocation'
- Line 94: Unsupported element 'AddressOnParent'
- Line 99: Unsupported element 'Description'
- Line 102: Unsupported element 'HostResource'
- Line 103: Unsupported element 'Parent'
- Line 104: Unsupported element 'AddressOnParent'
- Line 109: Unsupported element 'Description'
- Line 112: Unsupported element 'AutomaticAllocation'
- Line 113: Unsupported element 'Parent'
- Line 114: Unsupported element 'AddressOnParent'

After this I tried importing into VirtualBox and then exporting will checking the use Legacy OVF setting.  Which resulted in the following error:

E:\Documents and Settings\user\My Documents&gt;ovftool "Debian Server (32bit).ovf"
ian-server-32bit.vmx
Opening OVF source: Debian Server (32bit).ovf
Opening VMX target: ian-server-32bit.vmx
Error:
- Line 82: OVF hardware element 'ResourceType' with instance ID '7': No support
for the virtual hardware device type '35'.

Hi everyone,

I am trying to convert a VirtualBox 3.1.4 image with 2 harddisks with OVFTool 1.00 x64 linux.

~/VirtualBox$ ovftool --noDisks SDM-MANAGER.ovf SDM-MANAGER.vmx

Opening OVF source: SDM-MANAGER.ovf

Opening VMX target: SDM-MANAGER.vmx

Error:

- '3' of device 'vim.vm.device.VirtualIDEController' was found. Only '2' allowed

I cannot seem to find the solution for the problem. Could anyone help me on this?

I have added the ovf file to the post!

Kind Regards,

Jeroen van de Hoef

Not sure if I'm not getting the syntax correct, but I am attempting to export a vm in OVF format directly from a ESXi 4.1 host.

I have tried several different commands, but all have failed.

Any help with the Syntax to export the OVF directly from a Host would be greatly apprecaited.

ovftool --compress=9 "vi://host1/ha-datacenter/3PAR-LUN6/server1" "Z:\server1.ovf"

ovftool --compress=9  "vi://host1/DC1/3PAR-LUN6/server1/server1.vmx" "Z:\server1.ovf"

ovftool --compress=9  "https://host1/DC1/server1/server1.vmx" "Z:\server1.ovf"

Hi,

I have built a VM, using VMware Studio in OVA format. I defined some custom OVF environment properties in it.

After I built the VM, I opened the .OVF file to see the property values are appeared correctly. They look like the below

</ProductSection>

I deployed this OVF to a ESXi 4.0 server. Later exported the same VM to OVF format using OVFTool, using the command line

ovftool.exe vi://root:xxxxxxxxxxx@IP/vmname  "d:\Virtual Machines\imported-OVF\newVM.ovf"

After the export, I opened the newVM.OVF file and found that the properties (like product, vendor, version etc.) are not retained.

What could be the issue. Please suggest.

--Hemanth

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

Hi,

I'm having difficulty signing an OVA with a CA-signed cert:

* Does ovftool support CA 'code signing' certificates with the CA's provided intermediate?  After including both in the pem, openssl indicated it was valid but ovftool signing failed.

* The specs are a little unclear as to signing with SHA-256 certificate.  Is the --shaAlgorithm used for signing?

Thx.

4.2.0 is bundled into the current build of Fusion10:

ovftool --version

VMware ovftool 4.2.0 (build-6230482)

This version has a busted --allowAllExtraConfig flag, so some VMs will not export to OVA, instead you get a slew of errors like this one:

- Line -1: Unsupported value 'disk.EnableUUID' for attribute 'key' on element 'ExtraConfig'.

I want to set some properties to ovf files.

I use ovftool as bellow:

ovftool --prop:ip=10.32.23.123 --prop:dns=255.255.254.0

when this command has been executed without error showing, I still cannot see the property of ovf files.

Then I used ovftool myovffile.ovf

I still can not see the property I want to set.

what should I do?

Hello,

I created a virtual machine in virtualbox which I then exported to OVA format using the export.

In VMWare player I then opened the OVA file. The VM opened, I was able to start the virtual machine and test it. All is working correctly.

I now wanted to export the VMWare virtual machine to a OVF format using the ovftool.

I run the ovftool providing the source and target, the ovftool is throwing a "Failed to open file" error no matter which source I provide. It is very frustrating since even in the verbose log there is no indication about which file the program is failing to find.

The verbose log is not very long so I will post it below.

What am I missing??

======= Verbose log

2018-12-27T23:27:15.862-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] [SSL_DB] Using C:\Users\Gordynorth\AppData\Roaming\VMware\ovftool_SSLDB as SSL DB

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 2 (SIGINT)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 4 (SIGILL)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 22 (SIGABRT)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 8 (SIGFPE)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 15 (SIGTERM)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Initializing progress

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] OvfTool Version: VMware ovftool 4.3.0 (build-10104578)

2018-12-27T23:27:15.888-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Using home directory: C:\Users\Gordynorth\AppData\Roaming\VMware\ovftool.cfg

2018-12-27T23:27:15.894-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Curl Version: 7.59.0

2018-12-27T23:27:15.894-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Done initializing libs

2018-12-27T23:27:15.894-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Determining source

2018-12-27T23:27:15.895-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Determining target

2018-12-27T23:27:15.895-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Getting source

2018-12-27T23:27:15.896-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Opening source

2018-12-27T23:27:15.896-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] [Context::Context] started. No parameters.

2018-12-27T23:27:15.896-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] [VmxConsumerContext::VmxConsumerContext] started.

2018-12-27T23:27:15.897-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] .\ is not a file

2018-12-27T23:27:15.903-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Backtrace:

--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-10104578, tag: OVFTool, cpu: x86_64, os: windows, buildType: release

--> backtrace[00] vmacore.dll[0x001F6D2A]

--> backtrace[01] vmacore.dll[0x00064FD0]

--> backtrace[02] vmacore.dll[0x0006776E]

--> backtrace[03] vmacore.dll[0x0002533C]

--> backtrace[04] ovftool.exe[0x00013FB6]

--> backtrace[05] ovftool.exe[0x0003AF07]

--> backtrace[06] ovftool.exe[0x0023B3CF]

--> backtrace[07] ovftool.exe[0x0023F77B]

--> backtrace[08] ovftool.exe[0x0023EA12]

--> backtrace[09] ovftool.exe[0x00247641]

--> backtrace[10] ovftool.exe[0x000D16E7]

--> backtrace[11] ovftool.exe[0x00159CBF]

--> backtrace[12] ovftool.exe[0x000DAC7C]

--> backtrace[13] ovftool.exe[0x000DB954]

--> backtrace[14] ovftool.exe[0x003846C5]

--> backtrace[15] KERNEL32.DLL[0x00017E94]

--> backtrace[16] ntdll.dll[0x0006A251]

--> [backtrace end]

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