Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have created an OVA file from VirtualBox 4.2.12, and someone tried to import this ova file into VMWare ESX 4. When he was doing so, VMWare ESX 4 promopted:

Line 25: Unsupported hardware family 'virtualbox-2.2'.

I assumed that the OVA file can be universally imported into VirtualBox, VMWare Workstation and VMWare ESX, but now it turned out not the case.

Now, step back a little, I want to know: Is it possible to create from VirtualBox VM, an OVA or OVF file that can be imported into all of the following product without error?

  1. VMware Workstation 6 or above?
  2. VMware ESX 4 or above?
  3. VirtualBox 4.2.12 or above?
share|improve this question

closed as off-topic by Falcon Momot, Ward, mdpc, TheCleaner, MikeyB Sep 13 '13 at 19:43

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is a site dedicated to professionals; novice questions are off-topic. Please see the Help Center for more information on topicality. The best advice we can give you is to hire a professional to help you out." – Falcon Momot, Ward, mdpc, TheCleaner, MikeyB
If this question can be reworded to fit the rules in the help center, please edit the question.

    
why are you using such old versions? they're bound to impact on portability options. –  Chopper3 Sep 5 '13 at 7:47
    
I have checked the closed question serverfault.com/questions/448056/… , and not sure if there are better answers, so I started another question. –  PIM Geek Sep 5 '13 at 7:48
    
@Chopper3, which version of VirtualBox do you suggest I use? –  PIM Geek Sep 5 '13 at 7:49
    
Something Like isn't really good enough; messages are there for a reason. I think Chopper3 is referring to the old version of ESX not VB. –  Iain Sep 5 '13 at 7:53
    
I will verify that information, thanks for your help! –  PIM Geek Sep 5 '13 at 7:56

1 Answer 1

up vote 0 down vote accepted

There is an article on VMware knowledge base trying to explain a similar issue but on ESXi 5.x.

Try to modify the XML manifest of your OVA/OVF appliance:

  1. Open the OVA/OVF file in some editor
  2. Search for the XML Tag <VirtualSystemType>virtualbox2.2</VirtualSystemType>
  3. As you want to import it to ESX 4, replace the string virtualbox2.2 with vmx-06
  4. Try import again
share|improve this answer
    
I need to verify the method, and then I can accept the answer. :) –  PIM Geek Sep 5 '13 at 10:23

Not the answer you're looking for? Browse other questions tagged or ask your own question.