Search the VMware Knowledge Base (KB)
View by Article ID

Migrating a virtual machine configured with Virtual Hardware version 7/8 to an ESXi host with newer CPU generation fails with the error: The virtual machine requires hardware features that are unsupported or disabled on the target host (2109065)

  • 5 Ratings
Language Editions


  • Migrating a virtual machine configured with Virtual Hardware version 7/8 to an ESXi host with newer CPU generation fails.
  • You see an error similar to this on the destination host validation screen:

    The virtual machine requires hardware features that are unsupported or disabled on the target host:


This issue occurs because a destination ESXi host has a newer generation CPU with ISA extensions not available on the source ESXi host. It can also occur if the destination host has an older generation CPU lacking available extensions on the source host.


This is by design in VMware ESXi 5.x/6.0. When using Virtual Hardware versions 8 or earlier, ESXi performs a very strict checking of these extensions unless the virtual machine moves from or to a host with EVC enabled. Virtual Hardware versions 9 and later use more relaxed checking whether EVC is in use or not.

With the strict checking ESXi requires that extensions used by user level applications to match between the source and the destination. The more relaxed checking only requires that the destination should have all the extensions that have been exposed to the virtual machine. In this relaxed mode vMotions are not blocked, if the destination has other ISA extensions which have been not exposed to the virtual machine.

To resolve this issue, you must place either the source or destination host in an EVC-enabled cluster. If you cannot place the source or destination host in an EVC-enabled cluster, you may be able to resolve this issue by upgrading the virtual machine hardware version:
  • VMware highly recommends placing the source or destination ESXi host in an EVC-enabled cluster of any processor compatible type.  Be aware that the EVC cluster must support the same or a subset of the extensions available in the host you add, and that feature set must be the same or a superset of the extensions the virtual machine expects to use. For information on configuring EVC, see the Migrating Virtual Machines chapter in the Basic System Administration Guide for your ESX release.

  • You can alternatively, try to upgrade to Virtual Hardware version 9 (or later) in the virtual machine. Note, however, that this action will not help if the destination host does not support an extension that the VM has been exposed to. There may also be other limitations dependent on your particular environment:

    To upgrade the Virtual Hardware version of the virtual machine in the vSphere Client

    1. Power off the virtual machine.
    2. Right-click the virtual machine and click Upgrade Virtual Hardware.

    To upgrade the ESXi compatibility level (Virtual Hardware version) of the virtual machine in the vSphere Web Client:

    1. Select the virtual machine.
    2. Power off the selected virtual machine.
    3. Select Actions > All vCenter Actions > Compatibility > Upgrade VM Compatibility.
    4. Click Yes to confirm the upgrade.
    5. Select the ESXi versions for the virtual machines to be compatible with.
    6. Click OK.
    7. Power on the selected virtual machine.
For more information, see Enhanced vMotion Compatibility (EVC) processor support (1003212).

Additional Information

  • The vMotion of a virtual machine fails, it may behave differently after it is migrated to the destination ESXi host.
  • When  a virtual machine is migrated to another host, the destination host must offer all the features to the virtual machine that has been exposed to.
  • When using older virtual hardware versions in a non-EVC environment, the destination user-level CPU feature set must be identical to that of the source.
  • Virtual Hardware versions can further limit the features that a virtual machine can see. Mobility, the ability to migrate your virtual machine between hosts in the cluster, is enhanced by EVC.

    Note: In terms of features that the virtual machine is exposed to, this is different than features on the source hosts. For more information, see vMotion/EVC incompatibility issues due to AES/PCLMULQDQ (1034926).
For example: 
If a virtual machine boots on an ESXi host with a Westmere Generation CPU, then migrates to a an ESXi host with an Ivy Bridge Generation CPU. Then you consider migrating the virtual machine to an ESXi host with a Sandy Bridge Generation CPU, it has the features of the ESXi host with the Westmere Generation CPU that the virtual machine captured on boot that is valid and not the features of the source ESXi host with the Ivy Bridge Generation CPU.

See Also

Update History

02/08/2016 - Added ESXi 6.0 to Products.

Language Editions


Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 5 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 5 Ratings