VMware vSphere

 View Only

  • 1.  Import OVF Template - Line 25: Unsupported hardware family 'vmx-16'.

    Posted Aug 19, 2019 09:11 PM

    I have ESXi Embedded web client.

    Client version:

    1.33.1

    Client build number:

    12086396

    ESXi version:

    6.5.0

    ESXi build number:

    7388607

    I tried to import a OVF and VMDK file and got the following error: "Line 25: Unsupported hardware family 'vmx-16'."

    The vm i'm trying to import is from a vm created earlier this year in VMware Workstation Pro 15. Is there a resolution for this more specific than the options in the following older thread?

    Import OVF Template - Unsupported hardware family 'vmx-10'

    Why are VM's created in Workstation Pro 15, not compatible with ESXi 6.5?



  • 2.  RE: Import OVF Template - Line 25: Unsupported hardware family 'vmx-16'.

    Posted Aug 19, 2019 09:17 PM

    ESXi 6.5 only supports virtual hardware versions up to 13 (see https://kb.vmware.com/s/article/1003746).

    Depending on which virtual hardware components are used, you may be able to import the VM after changing "vmx-16" to "vmx-13" in the OVF file.

    André



  • 3.  RE: Import OVF Template - Line 25: Unsupported hardware family 'vmx-16'.

    Posted Aug 30, 2022 10:42 PM

    Obrigado ! Nota 10



  • 4.  RE: Import OVF Template - Line 25: Unsupported hardware family 'vmx-16'.



  • 5.  RE: Import OVF Template - Line 25: Unsupported hardware family 'vmx-16'.
    Best Answer

    Posted Aug 19, 2019 09:41 PM

    a.p. answer helped me see what i did wrong that caused this problem. Based on the documentation, i need to pay better attention to the hardware compatibility options i select when creating a virtual machine. The link he posted was super helpful so i could see what I should be choosing in the future.

    As for resolving the problem with existing VM's, VMware Workstation has a built in tool for this. Just go to the VM and then go to VM > Manage > Change Hardware Compatibility. Then follow the instructions. I made a clone first and then chose the option to "alter this vm" because i felt safer with that than doing the "make copy and change compatibility" route.  See docs here on this referenced from workstation v9 docs. That route was fast and easy and didn't require editing files manually or downloading additional software.

    ---------------------------------------------------------------------------------------------------------

    Was it helpful? Let us know by completing this short survey here.