?
Solved

vMotion CPU Modifying CPUID masks

Posted on 2010-08-17
5
Medium Priority
?
5,643 Views
Last Modified: 2013-11-11
Hello,

I have a cluster running four hosts using Westmere Intel processors (5630). I have added a server using processors 5530 in the same cluster.

When testing the vMotion I received an error regarding CPU compatibility.

I have found two knowledbase topics:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1993
and
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1991

I have changed the "ecx" for a guest to:
---- --0- ---- ---- ---- ---- ---- --0-
as described at the topic:

Group D
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").

Group E
Models include:
         
Intel Xeon CPUs based on Intel Westmere microarchitecture. For example, Intel Xeon 56xx Series ("Westmere-EP").

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

AES      a      ecx      ---- --0- ---- ---- ---- ---- ---- --0-

After changing those values, the error is the same.

Any ideas ?
0
Comment
Question by:maxihost
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 28

Accepted Solution

by:
bgoering earned 2000 total points
ID: 33460603
Configure EVC on your cluster as in the attached image. That will accomodate Nehalem and Westmere processor families.

Good Luck
evc.png
0
 

Author Comment

by:maxihost
ID: 33460656
Hello,

Its giving me the following error:


The cluster cannot be configured with the selected Enhanced vMotion Compatibility mode; CPU features disabled by that mode may currently be in use by powered-on or suspended virtual machines in the cluster.

0
 
LVL 28

Assisted Solution

by:bgoering
bgoering earned 2000 total points
ID: 33460695
That is true - if you have powered on VMs in "westmere" mode, or native mode on westmere if evc has never been configured, then you will have to power off all vms on the cluster in order to lower the evc mode. I know it is a hassle because I had to do that very same thing once with about 50 vms.

Sorry there isn't an easier way
0
 

Author Comment

by:maxihost
ID: 33460710
Oh my god. I have 75 VMs running. Ok. Thanks for the solution.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 33460729
LOL - I feel your pain. It has to be that way because vms that may (or may not) be using the features of the newer processor can become unstable when migrated to a cpu that doesn't support those features. You may be able to lessen the pain by moving all of your westmere hosts out of the cluster then setting the evc level.

Next you can power off and migrate vms one at a time back to your host in the cluster until one of your westmere hosts is empty, then add it back to the cluster where it will respect the new evc mode.

Repeat for your other three westmere hosts... You still have to power off each vm, but doing it this way they don't have to all be down at the same time.

Good Luck
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
A look into Log Analysis and Effective Critical Alerting.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
Suggested Courses

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question