Hi,
We’ve recently purchased a new HP DL360 G6 Server to add to
our ESX Cluster.
When trying to VMotion a VM to this ESX we get the following
error:
“Unable to migrate from ESX03 to ESX14: Host CPU is
incompatible…Mismatch detected for these features: RDTSCP;…”
I’m attaching a screen shot of the output of VMWare CPU
Info. You can see that we already have HP DL360 G5 servers in out cluster and
VMotion works fine. For some reason with the G6 it doesn’t although it seems
that (enabled) CPU features of the G5 and G6 are similar.
Any idea?
Enable EVC for cluster
---
VMware vExpert '2009
You could try to mask the inappropriate CPU setting or enable EVC for the cluster. This is one of the reasons why I always purchase Hosts in pairs.
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth VCP / vExpert
VMware Communities User Moderator
Blog: www.planetvm.net
Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]". Currently available on roughcuts
Forgot to mention that EVC is already enabled...
Take a look at this thread http://communities.vmware.com/thread/69579
---
VMware vExpert '2009
As you can see from the screenshot, we only have Intel CPU's.
Look closer at the screenshot and you will be able to see each CPU and server model on each ESX.
I also just noticed that none of the ESX has RDTSCP accoring to the table I attached.
just to clerify the current EVC cluster has 53xx and 54xx CPUs and we want to add 55xx CPU to the cluster
According with this KB you must able to add the 55xx ESX:
http://kb.vmware.com/kb/1003212
Be sure that VT is enabled on new node and that there aren't some custom CPUID Mask at VM level.
Andre
VT is enabled on all servers
But ESX03 and ESX14 are in the same EVC cluster?
From your screenshoot seems that one ESX is outside.
Is the source of the VMotion?
Andre
all ESX are in the same cluster.
currenly the dl360 G6(esx14) is out of the cluster but he was in the cluster when we tried to VMotion
No more ideas, sorry.
Just verify again that your VMs does not have custom CPUID Mask.
Andre
there are some customs CPUID mask that ware set by the EVC :
this is what is see in the vmx files :
cpuid.1.eax = "xxxx--
"
cpuid.1.ecx = "R--RR-RRRR-0--
cpuid.1.edx = "--
cpuid.80000001.eax.amd = "xxxx--
"
cpuid.80000001.ecx.amd = "--
cpuid.80000001.edx = "--R
"
cpuid.80000001.edx.amd = "---R
cpuid.1.ecx.amd = "R-----R
hostCPUID.80000001 = "00000000000000000000000120100000"
hostCPUID.1 = "0001067a00040800040ce3bdbfebfbff"
hostCPUID.0 = "0000000d756e65476c65746e49656e69"
guestCPUID.80000001 = "00000000000000000000000120100000"
guestCPUID.1 = "000006f800010800000022110febbbff"
guestCPUID.0 = "0000000a756e65476c65746e49656e69"
userCPUID.80000001 = "00000000000000000000000120100000"
userCPUID.1 = "0001067a00040800000022110febbbff"
userCPUID.0 = "0000000d756e65476c65746e49656e69"
evcCompatibilityMode = "TRUE"
Try to power off the VM, reset all CPUID Mask settings and try VMotion again.
Andre
Seems like my problem was in the fact that not all ESXes were updated to ESX 3.5 Update4 and also the VC needed to be updated to Update 4.