Direct import of vmware workstation virtual machines

[DeGarden]

VMware Workstation has an option to export virtual machines to OVF, however, they don't follow its specifications, even re-importing their ovf will fail.

So I request Virtualbox can directly import vmx virtual machines to vbox format or the one I choose between all available or suitable.

.ofv files generated by vmware workstation are not trustworthy and don't work when you import them into Virtualbox.

[Socratis]

So, let me get this straight... VMWare has a bug, and you want VirtualBox to work around the bug, by adding the "VMWAre import" capability, do I understand it right?

[DeGarden]

That's right. I don't think it's a bug actually, but lack of interest from vmware to get your vms out of their ecosystem.

[Socratis]

Have you actually complained to VMWare? You know they're part of the consortium that wrote the OVF/OVA specification, right?

[DeGarden]

Tech support expires 30 days after product purchase (although you have license to use workstation pro permanently), and without support they don't accept feedback. At most you can post in their forums but it's just for the "community".

I'm just an desktop end user, they aim mainly for enterprise, not much to do on my side here.

[Socratis]

Not sure what to say here... You want to fix the shortcomings/bugs in VMWare by having the VirtualBox developers do extra work, outside of their scope, adding more workload and potentially more bugs for a feature that their paid customers haven't asked for, neither have a need for.

Just open the VMX file with a text editor and try to replicate the setup in a new VM in VirtualBox. And use the existing VMDK as the VM's hard drive. Problem solved.

BTW, it's usually better and faster, if issues/concerns/questions get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.

[DeGarden]

bug tracker is the place to report issues

[Frank Batschulat (Oracle)]

Several issues with this request.

1) you don't even tell what the errors and shortcomings are that VMWare will produce for the OVF format. How and where you have observed the problems with a VMware produced OVF and how to replicate that perhaps.

2) How do you know the problem is that VMware produced a broken/wrong/insufficient OVF file at all? Which sections of the OVF spec are violated?

3) the VMX file format is propritary and private to VMware, it is not standardized or public in any way that I know about would define and declare that as an interface for 3rd parties to build upon.

​https://www.vmware.com/support/ws5/doc/ws_learning_files_in_a_vm.html
​https://www.petri.com/virtual_vmware_vmx_configuration_files

As it stands this report cannot get any more attention without more substantial content being provided.