Troubleshooting importing OVF Template into VMware ESXi

This post shows how to adapt a VMWARE OVA exported from Virtual BOX for a Virtual Machine, compatible with ESXi.

When you try to open an OVA with the VMware format on an ESXi you get the following error:

 “The OVF package requires unsupported hardware
Details: Line 25: Unsupported hardware family ‘virtualbox2.2’.”
Details: Line 25: Unsupported hardware family ‘_unsupported_version’.”

vmware1

Uncompresse OVA Archive :

First off all uncompress the OVA archive (with a zip extractor like 7-ZIP)

You will get a directory with 3 files on it like this :

VMFile.mf
VMFile.ovf
VMFile.vmdk

Modify the OVF file :

Open the *.ovf file (with Notepad+)

Change the following line :

 <vssd:VirtualSystemType>_unsupported_version</vssd:VirtualSystemType>

By this one :

 <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>

Modify the *.mf file and calculate the SHA1 hash of the modified OVF file:

Open the *.mf file which contains the SHA1 hash of *.ovf file. So you need to replace the value specified by the new SHA1 hash of .ovf file.

SHA1(VMFile.ovf)= 48432f9cb8b0bfa97098006abb390805449303be
SHA1(VMFile.vmdk)= ffa3500bc379a2e040badce315d6b3b06876d5a9

To calculate this hash you can use a tool like FCIV from microsoft. You can download it there : http://support.microsoft.com/kb/841290

>D:\FCIV\fciv.exe -sha1 "VMFile.ovf"
//
// File Checksum Integrity Verifier version 2.05.
//
da39a3ee5e6b4b0d3255bfef95601890afd80709 VMFile.ovf

So, put the new hash in the *.mf file and save it

SHA1(VMFile.ovf)= da39a3ee5e6b4b0d3255bfef95601890afd80709
SHA1(VMFile.vmdk)= ffa3500bc379a2e040badce315d6b3b06876d5a9

Maybe you may encounter other errors while importing the OVF template like:

Line XX: OVF hardware element ‘ResourceType’ with instance ID ‘5’: No support for the virtual hardware device type ’20’

This is a problem of SATA controller, change settings in ovf like this:

From this

<Item>
<rasd:Address>0</rasd:Address>
<rasd:Caption>sataController0</rasd:Caption>
<rasd:Description>SATA Controller</rasd:Description>
<rasd:ElementName>sataController0</rasd:ElementName>
<rasd:InstanceID>5</rasd:InstanceID>
<rasd:ResourceSubType>AHCI</rasd:ResourceSubType>
<rasd:ResourceType>20</rasd:ResourceType>
</Item>

With this
<Item>
<rasd:Address>0</rasd:Address>
<rasd:Caption>SCSIController</rasd:Caption>
<rasd:Description>SCSI Controller</rasd:Description>
<rasd:ElementName>SCSIController</rasd:ElementName>
<rasd:InstanceID>5</rasd:InstanceID>
<rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
<rasd:ResourceType>6</rasd:ResourceType>
</Item>

Other problems could happen if in the <Item> is listed an audio card, you should delete whole line starting from

<Item>
sound-card-settings
</Item>

Then save again OVF file.

Remember that every time you save the ovf file, and you what to try to import into ESXi, you must generate the hash, replace the hash in the .mf file, follow the steps above.

Deploy the new OVF :

Now, you can deploy directly the new OVF file on ESXi.
On VSPHERE select :

File > Deploy OVF Template
Select your OVF file :

The following WARNINGS are raised but you can move forward.

vmware2

So now you can deploy and start your VM.

Related Article: VIRTUALBOX OVA TO VSPHERE OVF | Uncompress a VMWARE OVA and modify its VM version | File Checksum Integrity Verifier

2 pensieri riguardo “Troubleshooting importing OVF Template into VMware ESXi”

  1. May I simply just say what a comfort to discover someone that really knows what they’re discussing on the internet.
    You definitely understand how to bring an issue to light
    and make it important. More people must look at this and understand this side of your
    story. It’s surprising you’re not more popular because you most cerrtainly have thhe gift.

Lascia un commento

Il tuo indirizzo email non sarà pubblicato. I campi obbligatori sono contrassegnati *

Questo sito usa Akismet per ridurre lo spam. Scopri come i tuoi dati vengono elaborati.