Migrate VMs to EVC Cluster without power off?

[romatlo32]

Hello folks,

We have new Cisco UCS servers with recent Intel Xeon generation processors - EVC enabled Sandy Bridge.

Our old cluster is HPE DL380 G9 and G8 - EVC disabled.

I am unable to migrate the VMs on old cluster while powered on because of CPU incompatibility.

I see this method for unlike hosts in the same cluster.  Moving vacated hosts to a new created cluster with EVC enabled, then moving VMs to it.

http://www.gabesvirtualworld.com/the-real-questions-about-evc/

I wondering if a third step could be added to then migrate to separate cluster of UCS hosts?

[a_p_]

We have new Cisco UCS servers with recent Intel Xeon generation processors - EVC enabled Sandy Bridge.

Our old cluster is HPE DL380 G9 and G8 - EVC disabled.

Which ESXi versions/build numbers are installed on these hosts?

What vCenter Server version/build do you use to manager the hosts?

Are the hosts patched to the latest BIOS (Intel-Microcode) updates?

I am unable to migrate the VMs on old cluster while powered on because of CPU incompatibility.

Please provide details. Does it show any incompatible bit masks?

André

[romatlo32]

Thank you for responding.

vCenter 6.5 build 6816762

vSphere 6.5 build 6765664

Intel Microcode updates:  I am not sure about the HPE servers, their BIOS is likely older, but the Cisco UCS hosts are updated to latest b200 M5 firmware 3.2.3h.

Error attached with feature details.

I've tried EVC Sandy Bridge and Westmere on the new cluster, but still error.  EVC is disabled on the source cluster.

[a_p_]

It looks like the Gen8 hosts have v2 processors, i.e. Ivy-Bridge CPUs, and the newer Gen9 hosts likely have Haswell, or Broadwell CPUs.

We have new Cisco UCS servers with recent Intel Xeon generation processors - EVC enabled Sandy Bridge.

Do the new host's CPUs support a later EVC mode, i.e. Broadwell? Do you have a special reason why you set EVC to Sandy Bridge?

For details about EVC modes, and CPU instructions, see https://kb.vmware.com/s/article/1003212

André

[RajeevVCP4 · Accepted solution]

Disable EVC first then try to migrate VM once done try to enable it

If it failed then only way power off VM then migrate

[romatlo32]

Thanks RajeevVCP4​

That was it.  I disable EVC on the target cluster and worked!

Maybe I am confused about EVC and vMotion. 

I guess you don't necessarily need EVC mode on to be able to vMotion to separate cluster with unlike processors?

In this case going from a HP DL380G9 Intel Xeon E5-2620 to a Cisco UCS b200 M5 Intel Xeon Gold 6140.

No issue, it just went.

Any extra comments to help me understand why this just works without extra help from EVC or otherwise?

[romatlo32]

Maybe because the target was EVC enabled originally and unable to step down?

[a_p_]

With setting the EVC mode to "Sandy Bridge" in the UCS cluster, you actually limited the processor features to those available with "Sandy Bridge", although the processors support more features. Disabling EVC in this case had a similar effect, as increasing EVC to e.g. Broadwell.

If all hosts have the same CPU, you don't necessarily need to enable EVC. Configuring EVC is required if different CPUs come into play, and you want to be able to live migrate VMs between them.

André