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

Skip to main content

My Subscriptions

Loading

Knowledge Base

vMotion CPU compatibility requirements for Intel processors (1991)

Last Updated: 6/15/2016Categories: TroubleshootingTotal Views: 277617Language:
Chinese (Simplified)Portuguese (European)JapaneseEnglish

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Details

This article outlines migrating virtual machines with vMotion across Intel processors, and the necessary steps to take to ensure compatibility.

Solution

In ESX 3.5 Update 2 and later, VMware recommends using Enhanced vMotion Compatibility (EVC) to eliminate many vMotion CPU compatibility problems. For more information on EVC, see Enhanced vMotion Compatibility (EVC) processor support (1003212).

To ensure system stability during migration with vMotion, VirtualCenter and vCenter Server require the source and target CPUs to be compatible. For more information on CPU compatibility requirements, see Basic System Administration for your version of vCenter Server or VirtualCenter, available from http://www.vmware.com/support/pubs/.

If the source and target CPUs are incompatible for vMotion, you can:

Perform a cold migration (rather than a vMotion migration), thereby removing vMotion CPU requirements as an issue.

Remove vMotion compatibility constraints by modifying the default bit-mask used by vCenter Server or VirtualCenter.

Note: That some modifications discussed in this knowledge base article are neither supported nor recommended by VMware for production environments. In general, masking any CPU features intended for applications (such as SSE3) is not supported for vMotion . Use of EVC is recommended for migrating virtual machines across CPU generations.

To obtain more information about a host system's CPU, you can use the CPU Identification Utility. VMware provides this as an ISO image file that can be uncompressed and used to create a bootable CD-ROM that provides CPU information about a host, even before an operating system or ESX/ESXi is installed. The latest version of this tool can be found on the VMware downloads page at http://vmware.com/download/shared_utilities.html.

This knowledge base article discusses vMotion compatibility constraints for Intel CPUs. For detailed information about how to apply the masks discussed in this article, see vMotion CPU Compatibility - Migrations Prevented Due to CPU Mismatch - How to Override Masks (1993). For information on AMD CPUs, see VMotion CPU Compatibility Requirements for AMD Processors (1992).

vMotion Compatibility Groups for Intel Processors

To guarantee successful migrations with vMotion, VMware has defined several compatibility groups based on processor family (Pentium 4, Core) and features introduced within those families.

By default, vCenter Server and VirtualCenter support vMotion migrations within each CPU compatibility group. For example, migration within group A is allowed, but migration from group A to group B or from group B to group C is not, as shown in the tables.

Intel Pentium CPUs

vMotionCPU Compatibility Group

CPU Details

ESX Server 3.x and ESX 4.x

ESX Server 2.x

Group A

Without SSE3, without XD (eXecute Disable).

Models include:

Intel P4s prior to Model 3, Stepping 1. For example, Willamette and Northwood.

Xeon and Xeon MP CPUs prior to Nocona, Q3 2004. For example, Foster, Prestonia, and Gallatin.

For A <-> B vMotion, apply SSE3 mask. (Not supported)

For A <-> B vMotion, apply SSE3 mask. (Not supported)

Group B
(Group B and C are the same for VC 1.x)

With SSE3, without XD.

Models include:

P4s from Model 3, Stepping 1 to Model 4, Stepping 1.

For example, Prescott, or numbered 5x0, 5x5, 5x9.

For B <-> C vMotion, apply NX mask.(Supported)

Group C
(Group B and C are the same for VC 1.x)

With SSE3 and XD.

Models include:

P4s after Model 4, Stepping 1 onward and Xeon and Xeon MP with 64-bit (EM64T) enabled.

For example, Irwindale, Cranford, Dempsey, Tulsa, or numbered 50xx, 70xx, or 71xx.

Intel Core CPUs

vMotion CPU Compatibility Group

CPU Details

ESXi 5.0, ESX/ESXi 4.x, ESX Server 3.x, and ESX Server 2.x

Group A

Without SSSE3, SSE4.1, SSE4.2 or AES.

Models include:

Dual-core Xeon LV based on Intel Core microarchitecture.

For example, Sossaman.

For A<->B vMotion, apply SSSE3 mask. (Not supported)

Group B

With SSSE3 only.

Models include:

Intel Xeon CPUs based on the Intel Core microarchitecture. For example, Intel Xeon 30xx, 32xx, 51xx, 53xx, 72xx, or 73xx.

For B<->C vMotion, apply SSE4.1 mask. (Not supported prior to ESX 3.5. Experimentally supported for ESX 3.5 and later only.)

Group C

With SSSE 3 and SSE4.1 only.

Models include:

Intel Xeon CPUs based on 45nm Intel Core microarchitecture. For example, Intel Xeon 31xx, 33xx, 52xx, 54xx, or 74xx.

For C<->D vMotion, apply SSE4.2 mask. (Not supported prior to ESX 3.5. Experimentally supported for ESX 3.5 and later only.)

Group D

With SSSE3, SSE4.1, and SSE4.2 only.

Models include:

Intel Xeon CPUs based on Intel Nehalem microarchitecture. For example, Intel Xeon 75xx Series, Intel Xeon 65xx Series, Intel Xeon 55xx Series ("Nehalem-EP"), and Intel Xeon 34xx Series ("Lynnfield").

For D<->E vMotion, apply AES mask. (Not supported prior to ESX 3.5. Experimentally supported for ESX 3.5 and later only.)

Group E

With SSSE3, SSE4.1, SSE4.2, and AES.

Models include:

Intel Xeon CPUs based on Intel Westmere microarchitecture. For example, Intel Xeon 56xx Series ("Westmere-EP").

Group F

With PCLMULQDQ, realmode, AVX, PCID and XSAVE.

Models include:

Intel Xeon CPUs based on the Sandy Bridge microarchitecture.For example, Inte Xeon E5 46XX, 26XX and 16XX.

Sandy Bridge processors are supported with ESX 5.0 and later only.

Group G

With ENFSTRG, F16C, FSGBASE, RDRAND and cpuidFaulting.

Models include:

Intel Xeon CPUs based on the Ivy Bridge microarchitecture.For example, Inte Xeon E3 1290V2.

Ivy Bridge processors are supported with ESX 5.0U1 and later only.

Applying the Masks

For information about how to apply masks referenced in the tables, see Modifying the Default Mask in vMotion CPU Compatibility - Migrations Prevented Due to CPU Mismatch - How to Override Masks (1993).

Warning: For production environments, VMware neither supports nor recommends modifying CPU masks for SSE3, SSSE3, SSE4.1, or SSE4.2, because of the risk of failure in applications or the guest operating system after migration. Experimental support is available for some masks in ESX 3.5 and later as noted. For more information on experimental feature support, see http://www.vmware.com/support/policies/experimental.html.

vMotion Between Single-Core and Multi-Core Processors

Migrations between single-core and multi-core Intel processors are supported, as long as the source and target CPUs have compatible CPU features (or the features are masked) as outlined in the tables above.

For More Information

For more information about the Intel Pentium 4 CPU family, see http://www.intel.com/support/processors/pentium4/.

For more information about Intel Xeon processors, see http://support.intel.com/support/processors/xeon/.

For more information about SSE3, SSSE3, and SSE4, see the Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1: Basic Architecture: http://www.intel.com/products/processor/manuals/

Note: Knowledge base articles 1991, 1992, and 1993 replace KB article 1377.

For related information, see Enabling EVC on a cluster when vCenter is running in a virtual machine (1013111).

Additional Information:

For translated versions of this article, see:

Español: Requisitos de compatibilidad de CPU de VMotion para procesadores Intel (2016325)

Português: Requisitos de compatibilidade da CPU VMotion para processadores Intel (2015884)

日本語: Intel プロセッサの vMotion の CPU 互換性要件 (2053215)

简体中文: Intel 处理器VMotion CPU 的兼容性要求 (2020948)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.0

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware VirtualCenter 1.4.x

VMware VirtualCenter 1.3.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX Server 2.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

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