VMware

This Question is Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
14 Replies Last post: Jul 2, 2009 7:53 AM by IT ST  

Unable to VMotion To HP DL360 G6 posted: Jun 29, 2009 5:51 AM

Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007
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;…”


vmotion.JPG


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.


vc02cpu.JPG


Any idea?

Tags: vmotion, migrate, dl360

Re: Unable to VMotion To HP DL360 G6

1. Jun 29, 2009 6:27 AM in response to: IT ST
Click to view Anton V Zhbankov's profile Champion
Anton V Zhban…
2,882 posts since
May 26, 2008
Enable EVC for cluster

---
VMware vExpert '2009
http://blog.vadmin.ru

Re: Unable to VMotion To HP DL360 G6

2. Jun 29, 2009 6:29 AM in response to: IT ST
Click to view tom howarth's profile Guru
tom howarth
7,351 posts since
Jul 25, 2005
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". Currently available on roughcuts

Re: Unable to VMotion To HP DL360 G6

3. Jun 29, 2009 6:35 AM in response to: tom howarth
Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007

Forgot to mention that EVC is already enabled...

EVC.JPG

Re: Unable to VMotion To HP DL360 G6

4. Jun 29, 2009 7:21 AM in response to: IT ST
Click to view Anton V Zhbankov's profile Champion
Anton V Zhban…
2,882 posts since
May 26, 2008
Take a look at this thread http://communities.vmware.com/thread/69579

---
VMware vExpert '2009
http://blog.vadmin.ru

Re: Unable to VMotion To HP DL360 G6

5. Jun 29, 2009 7:31 AM in response to: Anton V Zhban…
Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007

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.

Re: Unable to VMotion To HP DL360 G6

6. Jun 29, 2009 7:47 AM in response to: Anton V Zhban…
Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007
just to clerify the current EVC cluster has 53xx and 54xx CPUs and we want to add 55xx CPU to the cluster

Re: Unable to VMotion To HP DL360 G6

7. Jun 29, 2009 9:32 AM in response to: IT ST
Click to view AndreTheGiant's profile Guru
AndreTheGiant
5,942 posts since
Aug 28, 2008
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

Re: Unable to VMotion To HP DL360 G6

8. Jun 29, 2009 10:12 PM in response to: AndreTheGiant
Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007
VT is enabled on all servers

Re: Unable to VMotion To HP DL360 G6

9. Jun 29, 2009 10:19 PM in response to: IT ST
Click to view AndreTheGiant's profile Guru
AndreTheGiant
5,942 posts since
Aug 28, 2008
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

Re: Unable to VMotion To HP DL360 G6

10. Jun 29, 2009 10:32 PM in response to: AndreTheGiant
Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007

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

Re: Unable to VMotion To HP DL360 G6

11. Jun 30, 2009 5:56 AM in response to: IT ST
Click to view AndreTheGiant's profile Guru
AndreTheGiant
5,942 posts since
Aug 28, 2008
No more ideas, sorry.
Just verify again that your VMs does not have custom CPUID Mask.

Andre

Re: Unable to VMotion To HP DL360 G6

12. Jun 30, 2009 8:14 AM in response to: AndreTheGiant
Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007

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------------xx--------------"

cpuid.1.ecx = "R----R--R-RRRR-0-----------H-R--"

cpuid.1.edx = "---------------------------T----"

cpuid.80000001.eax.amd = "xxxx------------xx--------------"

cpuid.80000001.ecx.amd = "------------------RR-RR-----0---"

cpuid.80000001.edx = "----R---------------H-----------"

cpuid.80000001.edx.amd = "-----R--------------H------T----"

cpuid.1.ecx.amd = "R-------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"

Re: Unable to VMotion To HP DL360 G6

13. Jun 30, 2009 8:21 AM in response to: IT ST
Click to view AndreTheGiant's profile Guru
AndreTheGiant
5,942 posts since
Aug 28, 2008
Try to power off the VM, reset all CPUID Mask settings and try VMotion again.

Andre

Re: Unable to VMotion To HP DL360 G6

14. Jul 4, 2009 2:59 AM in response to: AndreTheGiant
Click to view IT ST's profile Novice
IT ST
22 posts since
Oct 1, 2007
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.

Actions

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities