OVF from Virtual Machine created on VMware Workstation can't be imported into VirtualBox 4.0.0 -> Fixed in SVN

[znmeb]

I have VMware Workstation 7.1 running on a 64-bit openSUSE 11.3 system. I built a 32-bit openSUSE 11.3 guest machine on VMware, then converted it to an "OVA" file with VMware's "ovftool".

znmeb@AlgoCompSynth:~/vmware/Project Kipling VMware> ovftool --targetType=OVA Project\ Kipling\ VMware.vmx . Opening VMX source: Project Kipling VMware.vmx Opening OVA target: . Writing OVA package: Project Kipling VMware.ova Disk progress: 2% Disk Transfer Completed Completed successfully znmeb@AlgoCompSynth:~/vmware/Project Kipling VMware>

Then I tried to import the resulting OVA file into VirtualBox 4.0.0. That didn't work - I got an error (PNG screenshot attached).

[znmeb]

Screenshot of error trying to import the OVA file

[Technologov]

Added myself as CC.

-Technologov

[poetzsch]

Could you attach the ovf file?

[znmeb]

OVF file (extracted from OVA file via tar)

[znmeb]

Hmmm ... error at line 105 ... let me try building the machine with no sound card and see what happens.

[znmeb]

I removed the sound card from the VMware-built VM, rebuilt the OVA with ovftool and got past this error. So I think all I'd expect from a fix for this bug is a more graceful way of dealing with a device that's not in the VirtualBox repertoire, like simply ignoring it with a warning message rather than crashing.

There's another error that happens with this import once the sound card is deleted, but that's a little more obvious and I'm going to file a separate bug report for it.

[poetzsch]

We fixed this by ignoring unknown types which are declared not required. Ignoring all unknown recourses types can lead to strange behavior of the imported VM. The fix will be included in the next minor version.