Deploying OVA developed in VirtualBox on ESXi/VMware

Discussions related to using VirtualBox on Windows hosts.
Post Reply
vw_mwa
Posts: 3
Joined: 1. Apr 2014, 21:47

Deploying OVA developed in VirtualBox on ESXi/VMware

Post by vw_mwa »

Hi all,

We developed a VM using the latest VirtualBox on a Windows machine and exported it as an .ova 2.0 Appliance. We are now trying to import it into ESXi using VMware Workstation, but are encountering the below errors. I did some googling and found a similar issue (see VirtualBox bug ticket #11160), but could not find a resolution to the problem. Any thoughts?

Thanks! :)
Image 1
Image 1
image001.png (15.46 KiB) Viewed 962 times
Image 2
Image 2
image002.png (7.41 KiB) Viewed 962 times
Image 3
Image 3
image003.png (67.02 KiB) Viewed 962 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Deploying OVA developed in VirtualBox on ESXi/VMware

Post by mpack »

If you have a problem doing something with VMWare software, you had best ask questions on a VMWare forum.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Deploying OVA developed in VirtualBox on ESXi/VMware

Post by scottgus1 »

Likely, either Virtualbox or VMware isn't sticking to the OVA format somehow. Unfortunately I don't know what that line is supposed to say. I'd suggest trying to export a machine from VMware and compare the lines to see what might be different.
Meanwhile, do you have to use the OVA system? You may be able to take note of the guest settings in Virtualbox, then set up the same settings in VMware as much as possible (Keep track of network card type, IO-APIC, no ISO's mounted in the virtual cd drive, no guest additions installed in the guest, etc...) Try to make the guest as generic as possible between the two systems, then copy the guest virtual disk file to the VMware host and attach it to a guest there with as close as possible settings. Boot it up and see what you get.
Post Reply