VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

VMotion CPU Compatibility - Migrations Prevented Due to CPU Mismatch - How to Override Masks for VirtualCenter 1.x

Details

This article provides information about overriding VMotion CPU compatibility restrictions between ESX Server hosts managed by VirtualCenter 1.x. For information on overriding VMotion CPU compatibility restrictions between ESX/ESXi hosts managed by VirtualCenter 2.x or vCenter Server 4.x, please see KB 1993.

Solution

By default, VirtualCenter allows migration with VMotion only between compatible source and destination CPUs. This article provides information about when it is appropriate to override CPU-compatibility constraints, how to override them, and provides links to additional information and resources.
 
Warning: VMware does not support or recommend modifying the VMotion constraints for CPU features that might be used by applications, such as SSE3, because of the risk of application or guest operating system failure after migration.

Modifying the Default Bit Mask

The VirtualCenter Server 1.x bit mask applies to all virtual machines on the ESX Server 2.x host system. VirtualCenter Server 1.x uses a locally stored text file, config.ini, for configuration information.

To modify the default bit mask for all ESX Server 2.x hosts managed by VirtualCenter Server 1.x, make the changes to the VirtualCenter Server’s configuration file (config.ini ). The process of editing the config.ini file is generally the same (regardless of CPU vendor):

  1. Log in to the Windows operating system of VirtualCenter Server as an administrator.
  2. Navigate to the VirtualCenter configuration directory. By default this directory is C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter.
  3. Open the config.ini file in a text editor.

    If the config.ini file does not exist, create it.
  4. Add the appropriate line for the CPU feature that you want masked to the config.ini file. See the Table below for more details.
  5. Save the file and restart the VirtualCenter Management Server Service so that the modified bit mask takes effect. The next time VMotion is attempted, the specific feature is ignored by VirtualCenter, and VMotion proceeds.

CPU Feature

VirtualCenter Server 1.x

Vendor

Supported?

SSE3

migrate.ignore.extfeature.bits = 0xE5BD

Intel, AMD

No

SSSE3

migrate.ignore.extfeature.bits = 0x4E7BC

Intel

No

migrate.ignore.feature.bits = 0x20000

SSE4.1

migrate.ignore.extfeature.bits = 0x8E5BC

Intel

No

Single-core-Dual-core

migrate.ignore.feature.bits = 0x90000000

AMD

Yes

PERF_MSR

migrate.ignore.extfeature.bits = 0xE5A0

Intel

Yes

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
As an example, to effectively enable VMotion between a host based on an Intel CPU that has SSE3 and one that does not,add:

migrate.ignore.extfeature.bits = 0xE5BD
 

Reverting to the Default CPU Compatibility Bit Mask

Revert to the default VMotion compatibility constraints by removing any of the lines added to the config.ini file and restarting the VirtualCenter Server.
 

Keywords

urlz

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (1 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? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (1 Ratings)   
Actions
  • KB Article: 1011354
  • Updated: Aug 14, 2009
  • Products:
    VMware ESX
    VMware VirtualCenter
  • Product Versions:
    VMware VirtualCenter 1.0.x
    VMware VirtualCenter 1.1.x
    VMware VirtualCenter 1.2.x
    VMware VirtualCenter 1.3.x
    VMware VirtualCenter 1.4.x