Resolving OVF Template Deployment Error on Older VMware ESXi Versions

byHasnain Zaidi •January 17, 2025

0

esxi 7 Line 25: Unsupported hardware family 'vmx-xx'.

While deploying an OVF template on older VMware ESXi versions (4.x - 6.x), you may encounter the following error:

"The OVF package requires unsupported hardware 'Unsupported hardware family vmx-##'."

This issue arises because the virtual hardware version specified in the OVF template isn’t compatible with the vSphere version currently in use. For instance, newer OVF templates are configured for hardware versions (e.g., vmx-10) that older ESXi versions cannot recognize.

Affected Systems

SecureAuth IdP Virtual Appliances running on VMware ESXi versions 4.x - 6.x
SecureAuth IdP Version: 7.x+
OS Version: Windows Server 2012 R2

Workaround Steps

Here’s how you can resolve the issue and successfully deploy the OVF template:

1. Extract the OVF Template Files

Locate the SecureAuthIdPAppliance-2012r2-vmware.X.0-vX.X-XXXXXXXX.ova file.
Use a tool like 7-Zip or WinZip to extract its contents into a folder named after the .ova file (e.g., SecureAuthIdPAppliance-2012r2-vmware.X.0-vX.X-XXXXXXXX).
After extraction, the folder should contain:
- .vmdk files
- A .ovf file
- A .mf file

2. Edit the `.ovf` File

Right-click the .ovf file and open it in a text editor (e.g., Notepad).

Locate the line:

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

Replace vmx-## with a hardware version compatible with your ESXi environment.
- For example, change vmx-10 to vmx-09 for compatibility with older versions.

3. Save the Changes

Save the edited .ovf file and close the text editor.

4. Update or Remove the `.mf` File (Optional)

The .mf file contains hash values for the OVF package components. If you modified the .ovf file, the hash value for it in the .mf file is now invalid.
Option A: Recalculate the SHA-1 hash for the edited .ovf file and update the corresponding value in the .mf file.
Option B: Simply delete the .mf file – this often works without causing issues during import.

5. Import the OVF Template

Use your usual process to import the OVF template into your VMware environment. The hardware version should now match the ESXi version, allowing the deployment to proceed.

Key Insights

Hardware Compatibility Matters: Always verify the hardware version of the OVF template against the supported versions of your ESXi environment.
Editing OVF Files Safely: Make backups of the original .ovf file before making changes, in case you need to revert.
Hash Files in OVF Packages: While the .mf file ensures integrity, it’s not always mandatory for the deployment to succeed.

Final Thoughts

This simple workaround ensures that even on older ESXi versions, you can successfully deploy OVF templates designed for newer hardware. If you’ve encountered similar issues or have additional tips for working with OVF templates, let’s discuss in the comments!