We help IT Professionals succeed at work.

vSphere 4 new Server - host cpu is incompatible with the virtual machine's requirements

ITdesk
ITdesk asked
on
Hi All,

We have 8 node vSphere 4 cluster in our organization.
all of the 8 nodes are Dell R710 with 2QC CPUs and 72 gigs of ram.

Recently, one of the servers had developed some hardware issues,
and since this is a production enviroment and the server's warranty was already over,
we replaced the server with a new server, still Dell R710.

after installing ESXi 4.1.0 (502767) on it,
and configured the networking,
we added the new server to our cluster.

When we try to move virtual machines (vmotion) to the new server,
we're getting this error
 
 vSphere Error
The new server has a Xeon 5620 CPU
While the other 7 servers has a Xeon 5520 CPU
also, the new server has a newer bios version than the other servers.

the new server is running ESXi 4.1.0 (502767) While the other servers are running ESX 4.1.0 (260247)

is there a way to make this cluster work properly?

Appreceate some help here,

Thanks! :)

Comment
Watch Question

Please see the following KB from Vmware as it talks about your problem running different CPU's

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1029785&sliceId=1&docTypeID=DT_KB_1_1&dialogID=256490769&stateId=0 0 256500120
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
You need to enable EVC Mode for your cluster.

Right Click your Cluster, Click Edit Settings

Select VMware EVC, and select Change EVC Mode.

for your processors Xeon 5620 & 5520 CPU, you would select Intel® Xeon®
45nm Core™2 EVC Mode


See here

http://kb.vmware.com/kb/1003212
http://kb.vmware.com/kb/1005764

 Enable Intel® Xeon® 45nm Core™2 EVC Mode
You will need to make sure, that before you enable, there are NO VMs, on the host you enable, because EVC Mode cannot be set with VMs, that are powered ON, on the host.
Yep hanccoka is right, that is exactly what the KB i listed suggests to do!
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
It's not a problem EVC has been developed for this specific reason of mixing and mathing old and new processors.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
also the error message, also states which KB you need to look at to enable an EVC cluster.

Author

Commented:
Hi guys,

When i'm trying to set EVC mode,
i'm getting a compatibility warning

EVC Error
Is this warning suggesting me to turn off all my wirtual machines before changing this?
is there an option to change it to one or two ESXs at a time?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
In my Post I stated

"You will need to make sure, that before you enable, there are NO VMs, on the host you enable, because EVC Mode cannot be set with VMs, that are powered ON, on the host."

Correct. No because it's a Cluster function.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
what you can do, is create a New Cluster, Call it New Cluster, edit Cluster and enable EVC Mode.

and then drag and drop an existing ESX host with NO VMs, or Powered OFF VMs into the New Cluster repeat for all hosts.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
delete old cluster, and then rename the new cluster.

Author

Commented:
i created a new cluster and attached the new server (the one with the different cpu) to it.
when I'm trying to migrate a virtual machine to the new cluster i'm still getting the cpu incompatability warning.

no other way to do this without turning of virtual machines?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
Yes, because there is still a mismatch.

Now vMotion VMs off one "old cpu server" to another "old cpu server" and then move that "old cpu server into the new Cluster" - But there is no getting around it, eventually the last server which has ALL the VMs, VMs must go off!

.The issue is HOT vMotion, you'll have no issue moving a machine that's off!

Eventually some VMs must go OFF. It cannot set the CPU bits, whilst a VM is ON!

Author

Commented:
Thank you all.

The migration to the new cluster was completed.
All of my VM's are running in the new cluster with EVC mode enabled,
and hot vMotion between 2 different cpu hosts is working fine.

Thanks Again!