OVF format: import from VirtualBox-4.3 to WMware Workstation-10.0 does not work

[asashnov]

I tried to migrate virtual machine from VirtualBox-4.2 to VMWare 10.0

but without success.

KB article seems to be wrong or non actual:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=205386...

I tried to migrate "Debian 6 x32" virtual machine

from  Oracle VirtualBox 4.3 under Ubuntu 12.04 x32

to   VMware Workstation 10.0.4.2249910 under Debian 7 x32

While exporting to OFV format I tried all thee options.

If I export to OVF 0.9 after clicking 'Retry' I get:

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

Error importing OVF: The import operation failed with more than 5 errors. The ovf you are trying to import is probably corrupt or an unsupported legacy version. The first 5 errors are shown below:

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'

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

If I export to OVF 1.0 after clicking 'Retry' I get:

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

Error importing OVF: Capacity mismatch for disk /home/user/vmware/bdeb60x32//bdeb60x32-disk1.vmdk

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

If I export to OVF 2.0 after clicking 'Retry' I get:

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

Error importing OVF: Line 2: Incorrect namespace 'http://schemas.dmtf.org/ovf/envelope/2' found

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

[WoodyZ]

Here is a workaround...  Extract the contents of the .ova file and then use only the .vmdk file after you first convert it to the proper type for use under VMware Workstation with vmware-vdiskmanager.

When exporting to OVA/OVF the exported .vmdk file is of type 5 (streamOptimized), and in normal use under VMware Workstation should be of either type 0 (monolithicSparse), 1 (twoGbMaxExtentSparse), 2 (monolithicFlat) or 3 (twoGbMaxExtentFlat).

vmware-vdiskmanager -r sourceDisk.vmdk -t N destinationDisk.vmdk

Where N is either 0, 1, 2 or 3.

Note that the sourceDisk and destinationDisk may not have the same name in the same folder, so if you want to maintain the name then use the fully qualified pathname of different locations as necessary.

Once you've converted the sourceDisk.vmdk from a type 5 (streamOptimized) to type 0~3 you can then create a new VM using an existing disk, the newly created destinationDisk.vmdk virtual disk.

[maxmaster]

VMware Documentation is WRONG.

VMware Workstation 10 Documentation Center

For example, you can import OVF virtual machines exported from VMware Fusion™ or Oracle VM VirtualBox into Workstation. You can import OVF 1.0 and later files only.

Importing OVF 2.0 files does NOT work.

[johnball]

Will someone will ever fix this [snip] bug every user using VMWare+VBox encounters on a daily basis ?

This is a real disgrace!

edit by wila‌ , removed expletive as per Community Terms of Use

[nyjak]

I'm having problems with this as well, importing into the latest Workstation from Virtualbox. I get .OVF format errors and the size mismatch with version 1.0.

FIX REQUESTED!

[TwoScoops72]

I had a ton of issues converting from virtualbox to vmware workstation.  I was able to sort it out after a bunch of failed attempts from many different forums.

Hope this helps others.

Convert from VirtualBox 5.0.20 to VmWare Workstation 11.1.0(probably works with a wide range of versions).

Export the ova from virtualbox

• Open virtualbox, make sure guest you want to export is not running.
• Highlight guest, file--> Export Appliance
• Select OVF 1.0 and check 'Write Manifest'
  • ovf v2 did not work for me

Extract the ova file using 7zip or other compatible extract utility.

#######################################################

Convert the vmdk file(s):

• Open a cmd prompt and navigate into your vmware folder to find the vmware-vdiskmanager.exe
• In my case it was in 'c:\program files (x86)\vmware\vmware workstation' folder.
• use the vdiskmanager.exe utility to convert the existing vmdk file(s) to a format that vmware likes better...

run this:

vmware-vdiskmanager -r <sourceDisk>.vmdk -t 2 <targetDisk>.vmdk

http://www.vmware.com/pdf/VirtualDiskManager.pdf‌

• Where sourcedisk is in the extracted ova from virtualbox and targetdisk is the location of where you want the export to happen.
• I used the same filename for source and target, not sure if this matters or not.
• I did get a warning each time I did this but it did not cause any problems for me.
  • VixDiskLib: Invalid configuration file parameter.  Failed to read configuration file.

#######################################################

After converting the disk:

1. Create a new virtual machine, advanced and use existing hard disk
2. point to the converted disk(I selected the larger vmdk file, not the 'flat' version that was 1k)
3. Make that disk SATA instead of SCSI(SCSI caused bluescreen when it tries to boot in my scenario).
4. Select 'Convert' rather than 'Keep existing format'

Now launch the VmWare Workstation and start up your image and cross your fingers.

#######################################################

If successful:

You should uninstall virtualbox programs after first startup.

Then install the vmtools

[stock1337]

i am using fusion and soemhow google land me this page.

A shorter method is below:

extract the vmdk file from ova .  Create a custom vmware image.  Select the correct operating system (or as close as possible). 

Then when it ask for creating new disk or existing vmdk, select the previously extracted vmdk file . Then just follow default selection.

reboot and everything work.     

[hookshy]

edit .ovf file and under <Disk ovf:capacity="12345678900000"

just enter some random numbers : ENJOY !!!

- add some 0 to the actual size to increase the size of the vmdk 

[Godaddy143]

Good job man 👍👍

[magotel]

When you go to export from the virtual box, it gives you the option to choose a format; 0.9 or 1.1 versions. I chose v1.1 for my CSI ova on the virtual machine and it was converted straight to another ovs file of the format I chose and to a dir of my choice. I then uploaded this into my VMware Workstation Player 17 and it is working perfectly.

GM.