VMware Cloud Community
jlalvarado
Contributor
Contributor
Jump to solution

Unable to VMotion between DL380-G5 (e5345 2.33Ghz) and DL380-G5 (e5450 3.0Ghz)

Hello Everyone,

We recently added to new ESVMX Servers to an existing cluster, servers are DL380-G5 Quad E5450 model. These new servers are unable to VMotion with the existing ESX Servers in the cluster, existing servers are DL380-G5 Quad E5345 model. Has anyone ran across this issue? I installed VMotion Info and the instruction sets seem to be the same.

Exact error message: The CPU of the host is incompatible with the CPU feature requirements of virtual machine; problem detected at CPUID level 0x1 register 'ecx'.

Reply
0 Kudos
1 Solution

Accepted Solutions
weinstein5
Immortal
Immortal
Jump to solution

With u2 vmware has added what they EVC - Enhanced VMotion Compatability - that possibly can handle this CPU incompatibility a little - if you are not running u2 than the CPUs need to be compatible - I believe HP maintains a vmotion copatbility chart on their website -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

View solution in original post

Reply
0 Kudos
8 Replies
DeafMCSA
Enthusiast
Enthusiast
Jump to solution

You might be able to do a "Off-Line" VMotion/Migration. However you would not be able to do a "Live" VMotion. VMWare states that you must have same hardware, usually they mean same CPU. Hope this may help.

Reply
0 Kudos
DeafMCSA
Enthusiast
Enthusiast
Jump to solution

What I mean "Off-Line" VMotion, shutdown or turn off the VM and move that vm to the other host.

Reply
0 Kudos
timw18
Enthusiast
Enthusiast
Jump to solution

I often have these issues when you have 2 different models which have different CPUs in them. Please see the attached document for possable solutions.

Reply
0 Kudos
BigHug
Enthusiast
Enthusiast
Jump to solution

They are not vmotion compatible. I think you have to mask out sse4 on the E54xx to make it work.

Reply
0 Kudos
weinstein5
Immortal
Immortal
Jump to solution

With u2 vmware has added what they EVC - Enhanced VMotion Compatability - that possibly can handle this CPU incompatibility a little - if you are not running u2 than the CPUs need to be compatible - I believe HP maintains a vmotion copatbility chart on their website -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
jlalvarado
Contributor
Contributor
Jump to solution

We in fact created a new ESX 3.5U2 EVC enabled cluster starting with the e5450 servers. We then upgraded each e5345 to ESX3.5u2 and VMotioned the virtual machines from the original cluster onto the EVC enabled cluster. We are now able to VMotion between the e5345 and e5450 chipsets.

Thank you everyone for your assistance. Please feel free to reach out to me if you need further explanation.

Reply
0 Kudos
jlalvarado
Contributor
Contributor
Jump to solution

Thanks BigHug for your response. We ended up upgrading all the servers

to ESX 3.5u2 and created a new Cluster with EVC enabled and then

vmotioned all the VM's into the new Cluster and now we are able to have

both e5345 and e5450 chipsets live together in the same cluster with

vmotion compatibility. All this with zero impact to the virtual

machines.

Thanks,

Jose L Alvarado

Manager, Server Engineering

MediaWorks, NBC Universal

Office (818) 777-2441 | Mobile (818) 266-5523

Reply
0 Kudos
NTShad0w
Enthusiast
Enthusiast
Jump to solution

in esx 3.x and 4.x you can always use cpuid mask changing (if for example VMware EVC did not work (for me for example not working because I have some old servers).

CPUID mask changing You doing in properties of every vmachine (yep this is disadvantage) Options\CPUID Mask\Advanced

info about usage here you can find in googl by typing: vmware cpuid mask change

kind regards

Dawid Fusek

Reply
0 Kudos