Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"The virtual machine requires hardware features that are unsupported or disabled on the target host" when migrating a virtual machine (65151)

Last Updated: 2/28/2024Categories: TroubleshootingTotal Views: 22397Language:
Chinese (Simplified)JapaneseEnglish

13 like this article

Subscribe to get an email
newsletter with new updates

13 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Migrating a Virtual Machine from one host to another host fails with the below error message :
The virtual machine requires hardware features that are unsupported or disabled on the target host. If possible, use a cluster with Enhanced vMotion Compatibility enabled (EVC)
CPUID details: incompatibility at level 0xx register 'xxx'
Host bits: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Required: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx

Cause

This issue occurs because the target host does not provide the same or greater level of CPU features as the source host. Typically, this is because the destination host uses an older CPU family, an older revision of the same CPU family, or the destination host CPU is from a different manufacturer.

In the absence of Enhanced vMotion Compatibility (EVC), virtual machines cannot be migrated to hosts whose CPUs do not provide the same or greater capability and features. When a VM is powered on, it will consume all available CPU features and capabilities on the origin host. These cannot be removed transparently and thus the absence of equivalent or superior features or capabilities on the destination host will cause vMotion migrations to fail.

Resolution

Power down the VM and migrate it to the desired target before powering back on(i.e. Cold Migration).

To Configure EVC on the cluster

VMware Documentation (6.7 and later ) - Enable EVC on an Existing Cluster

For more information about EVC support and implications, see VMware EVC and CPU Compatibility FAQ (1005764) process support

Note:  Until you power-off and then power on the Virtual Machine new features are not available to the Virtual Machine and cannot access any new features that are added until the Virtual Machine is power-off. A reboot of the guest is not sufficient.

Refer to the following link for steps to configure EVC mode, “The target host does not support the virtual machine’s current hardware requirements” error vMotioning a VM (1003212).

Workaround

In the case of a specific VM see EVC mode mismatch causes virtual machine migration failure for specific VM/VMs for a solution.

Related Information

Enhanced vMotion Compatibility (EVC) processor support
EVC and CPU Compatibility FAQ
Enabling and managing EVC on ESXi clusters in vCenter Server 5.x and 6.0
Adding an ESXi host with an older CPU than the current EVC baseline

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
使用 PSC HA 时如何融合为具有嵌入式 Platform Services Controller 部署的 vCenter Server Appliance (65129)

KB
•
ESXi/ESX の構成の上限 (1003497)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant