Monday, September 3, 2012

commons.ova deploy error on vmware esx - Unsupported hardware family 'virtualbox-2.2'

I downloaded Perforce commons OVA file commons.ova and when I tried to deploy it on VMWare ESX server, it failed with the error
Error: OVF Package is not supported by target: - Line 25: Unsupported hardware family 'virtualbox-2.2'.

Here the issue is with the commons.ovf file inside commons.ova . It defined virtual system type as virtualbox-2.2, which is a Oracle Open source virtualization product. Hence VMWare doesn't understand it.

We need to change it from virtualbox-2.2 to vmx-04 a VMWare format in that file.

Here are the steps to modify .ovf file inside .ova on linux system

  • Copy .ova file (commons.ova) to a Linux system
  • Extract ova file using tar utility
            tar xvf commons.ova

       Now you will get the following files
           commons-disk1.vmdk  commons.ovf
  •  Edit the .ovf file (commons.ovf) and do following changes 
               vi commons.ovf   (change the below line as shown)
            1) Replace  virtualbox-2.2 with  vmx-04
            2) To fix the error Line 66: OVF hardware element 'ResourceType' with instance ID '5': No support for the virtual hardware device type '2
  changed this item:

        <rasd:Description>SATA Controller</rasd:Description>

into this item:

        <rasd:Description>SCSI Controller</rasd:Description>
  • Convert ovf back to ova again. You should have installed 'ovftool' utility on your machine
           ovftool commons.ovf commons.ova

        Deploy it on your ESX server now. There shouldn't be any issue.


Retiredfeline said...
This comment has been removed by the author.
Ken Yap said...

Thanks, this fixed my problem. One thing for others to note, do not blindly copy the SCSIcontroller element like I did. You must retain the original InstanceID from the SATAcontroller element or your virtual disks will not be attached to a controller.

Unknown said...

I got other error

Detail Line 119:OVF hardware element 'ResourceType' with instance ID '10'. NO support for the virtual hardware devide type '35'



Sound Card



Can anyone give me the solution for this?

Anonymous said...

@Omkar Nimja - I believe that you can just remove that entire block safely. Or so I've semi-deciphered from this blog post

sectia said...

Thanks for sharing this. I've a different solution to the issue:

from the command line run ovftool with the --lax flag which turns errors into warnings. Doing this you will be solving the issue as well.

ovftool --lax VM.ova dirforVMX/



Anonymous said...

Awesome! It worked like charm. Thanks a lot!

Unknown said...

Thanks. This helped me. I also want to bring attention to a related issue:

"The DMTF RASD specifies a set of fields that can be set. We only a subset of those fields in an OVF descriptor. The fields in a RASD must be ordered alphabetically."