Loading

×Sorry to interrupt
CSS Error

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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Troubleshooting vMotion CPU feature requirement error messages (1003718)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 38670Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When performing a VMotion migration one or more of the following compatibility errors are displayed:

Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x80000001 register 'edx' .

Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x80000001 register 'ecx' .

Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x1 register 'ecx' .

Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x1 register 'edx' .

Purpose

This provides information on vMotion CPU feature requirement error messages that can occur when trying to migrate virtual machines.

Also, this article provides troubleshooting steps to help eliminate the common causes for the different error messages when they prevent migration of virtual machines.

Resolution

Overview

VMware does not virtualize the CPU in virtual machines and therefore, by default VMware VirtualCenter only allows VMotion migration between CPU's that have similar features. This means that the CPUs need to have the same manufacturer (AMD or Intel), be of the same family (Pentium, Xeon, etc.), and have common extended features between the ESX Servers involved in the VMotion. A restriction has been put in place to prevent migration between servers that have substantially different CPUs due to the risk that the virtual machine could crash during the migration.

Note: This only applies to VMotion migrations, cold migrations where the virtual machine is powered off are not affected by CPU feature requirement compatibility.

Workaround

To workaround the behavior check the following:

Ensure that your hosts have CPUs that are compatible, to allow vMotion. For specific information about Intel and AMD CPUs and vMotion compatibility, see:

vMotion CPU Compatibility Requirements for Intel Processors (1991) .

vMotion CPU Compatibility Requirements for AMD Processors (1992) .

Ensure the hosts have the same features turned on in the BIOS of the Servers. If there is a mismatch between the servers BIOS configuration even if they are physically identical, they still show a compatibility error message. The two most common features to check are Non-Execute Memory Protection (NX / XD) and Virtualization Technology (VT / AMD-V).

Notes:

- On an ESX host, you can check if the NX/XD is set by looking at the flags line in the /proc/cpuinfo file. For further information, see Checking cpuinfo information on an ESXi host (1031785).

- To determine if Intel or AMD-V are enabled in the bios without rebooting, see Determining if Intel Virtualization Technology or AMD Virtualization is enabled in the BIOS without rebooting (1011712).

- If the BIOS of a server has been recently updated or a new server added to the environment ensure to recheck these settings. BIOS upgrades can reset or disable custom configurations.

Turn off the virtual machine and perform a cold migration. With a cold migration VirtualCenter does not check the compatibility of the CPUs because they are not actively being used at the time of migration. When the migration is complete power on the virtual machine on the destination host.

Overriding CPU compatibility constraints

In some scenarios, it may be necessary to override the masks to allow vMotion migration to occur. VMware provides a limited ability to be able to override compatibility constraints, by masking certain CPU features from the virtual machine.

Caution: VMware recommends against overriding CPU compatibility constraints due to the risk of application or guest operating system failures after migration.

For instructions on how to apply and a listing of supported CPU feature masks, see Migrations with VMotion Prevented Due to CPU Mismatch -- How to Override Masks (1993).

Related Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box
Determining if Intel Virtualization Technology or AMD Virtualization is enabled in the BIOS without rebooting
Checking cpuinfo information on an ESXi host
VMotion CPU 機能の要件エラー メッセージのトラブルシューティング
对 vMotion CPU 功能要求错误消息进行故障排除

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Windows 服务器的 P2V 转换在完成 1% 时失败 (2006659)

KB
•
物理から仮想に変換後の Windows 2003 仮想マシンの高い CPU 使用量 (1007172)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant