Vmotion error due incompatible CPUID

[michele_distasi]

Hi ,I had a cluster with two IBM x3850 each with 2 Intel(R) Xeon(TM) CPU 3.00GHz

Yestarday I added an IBM x3650 with a quadcore processor and when try to migrate a vm I get an error of incompatibility of the cpuid. I read the kb 1993 but I have trouble understanding how to change the mask. Could you give me some help?

This is the screenshot of error and cpuinfo.Thanks.

[arturka]

hi

did you enabled EVC on cluster ? this is the quickest way to avoid situation like yours

visit my blog

www.vmwaremine.com

[Mohammad1982]

This is exactly what you need

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101129...

[Varunsh]

Perform the checks, if you have EVC compatible CPU

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100321...

If yes enable EVC if no proceed further

recommendtaion : Source and destination should have the same manufacture

[Basheer09]

Hi Michele,

By the above post you might now know that solution is to enable EVC on cluster.

Please find the below steps for understanding EVC and implementing it.

1. Why you got the error ?

--> Since the processor model/family for IBM x3850 will be different from you IBM x3650, vMotion will consider this as different CPU sets and will fail with error Host incompatiblility error.

2. Why EVC fixes this ?

--> EVC creates a CPU Base line with considering the lower featured processor as standard, So that VM running on the ESX hosts thinks that it has same underlying hardware with exact same feature as the source ESX host.

4. How to implement EVC ?

--> You need to move all the ESX's out of the cluster.

--> Enable EVC on the Cluster.

--> If vMotion fails again with longmode bit or XD bit, Put the ESX in maintenance mode and reboot --> enter in BIOS of ESX --> Enable Intel VT or AMD-V with NX / XD bit in the BIOS of ESX servers. Power cycle

5. EVC drawback :

--> Even if you purchase a CPU with high processor features, You will be ending up using the older ESX CPU features on the host. Newer features will be suppressed.

6. Suggestions : Always use the same set of hardware with same CPU model in cluster.

Kindly consider awarding points if this information is useful.

[michele_distasi]

Thanks for the answers, but I still have problems. I set the on the new host the Execute Disable Bit enabled. I created a new cluster with EVC enabled and inserted the new host.Powered off a VM on the original cluster,and moved it to the new cluster, I powerd it on and tried to migrate it on one of the old hosts and I have the error in the picture.

[michele_distasi]

Yesterday I removed a host from the original cluster and tried to insert it in the new clustering with EVC enabled but I got the error that the host hardware cpu does not support EVC. ESX 3.5.0 is at level of 176894, I have to update it?

[arturka]

Hi Michele,

Deffiniatellyyou should update you whole VI infrastructure, because your server build is very old.

Start with VC server, apply the lastest Update (i think SP6) and then update your ESX hosts, this should help

visit my blog

www.vmwaremine.com

if my answer it's useful click some stars

[Basheer09]

For this you need to hide the NX/XD bit in the VM Settings.

Power off the VM --> Goto VM settings --> Options --> Advanced CPU options --> Hide NX/XD bit to the guest.. --> then do vMotion.

Kindly consider awarding point if this info is useful

[Basheer09 · Accepted solution]

For this error message host not support EVC cluster, Please follow the kB Article. http://kb.vmware.com/kb/1003212

And when you enable EVC choose the baseline as Intel® Xeon® Core™2

Kindly consider awarding point if this information is useful.