Cluster with different CPU architecture?

[jadedpuppy]

We have an existing 3 node ESXi 5.5 cluster, with Intel E5-2690 v3 CPUs installed.  The v3 is from the Intel Haswell family, and has 12 cores. EVC is turned on for the cluster, and set to Merom Generation level (I know, I know.  It was a mistake when we created the cluster and we just haven't had a chance to increase the EVC level yet).  I was thinking about adding another host to this cluster, but since they don't make the v3 anymore, I would have to purchase a E5-2690 v4 instead.  The v4 is from the Broadwell family, and has 14 cores.

I believe I will be fine for live vMotions as long as we don't try and increase the EVC level higher than Haswell.  Is this correct?

[rcporto]

I believe I will be fine for live vMotions as long as we don't try and increase the EVC level higher than Haswell.  Is this correct?

Yes, you're correct. And  I suggest you create a new cluster with EVC level to Haswell, add the new host, and then migrate the virtual machines from the old cluster to the new cluster and move the hosts from the old cluster to the new one. With that approach you will move virtual machines and hosts to the new cluster that will be at Haswell level.

[RAJ_RAJ]

Hi ,

Hope below list will help you to configure the cluster with EVC

EVC	introduced	Baseline	µarch	aka.	CPU Series
L0	vSphere 4.0	Merom	Core	Conroe Tigerton Woodcrest Clovertown Kentsfield	30xx Series 32xx Series 51xx Series 53xx Series 72xx Series 73xx Series
L1		Penryn		Dunnington Harpertown Yorkfield Wolfdale	31xx Series 33xx Series 52xx Series 54xx Series 74xx Series
L2		Nehalem	Nehalem	Beckton Gainestown Bloomfield Lynnfield Clarksfield	34xx Lynnfield 35xx Series 55xx Series 65xx Series 75xx Series i3-2100 Series
L3	vSphere 4.1	Westmere		Gulftown Clarkdale Arrandale	i3/i5 Clarkdale 34xx Clarkdale 36xx Series 56xx Series E7-2800 Series E7-4800 Series E7-8800 Seriee Core i7-620LE
L4	vSphere 5.0	Sandy Bridge	Sandy Bridge		E3-1100 Series E3-1200 Series E5-1400 Series E5-1600 Series E5-2400 Series E5-2600 Series E5-4600 Series
L5	vSphere 5.1	Ivy Bridge			i3-3200 Series i7-3500-LE/UE Series i7-3600-QE Series Xeon E3-1100-C-v2 Series Xeon E3-1200-v2 Series Xeon E5-1400-v2 Series Xeon E5-1600-v2 Series Xeon E5-2400-v2 Series Xeon E5-2600-v2 Series Xeon E5-4600-v2 Series Xeon E7-8800-v2 Series Xeon E7-4800-v2 Series Xeon E7-2800-v2 Series
L6	vSphere 6.0	Haswell	Haswell		E3-1200-v3 Series E5-1400-v3 Series E5-1600-v3 Series E5-2400-v3 Series E5-2600-v3 Series i3-4300 Series i5-4500-TE Series i7-4700-EQ Series
L7	vSphere 6.5	Broadwell
		Skylake	Skylake

ntel CPU Series EVC Interoperability Matrix

	EVC L0 Merom	EVC L1 Penryn	EVC L2 Nehalem	EVC L3 Westmere	EVC L4 Sandy Bridge	EVC L5 Ivy Bridge
Xeon 30xx Series
Xeon 32xx Series
Xeon 51xx Series
Xeon 53xx Series
Xeon 72xx Series
Xeon 73xx Series
Xeon 31xx Series
Xeon 33xx Series
Xeon 52xx Series
Xeon 54xx Series
Xeon 74xx Series
Xeon 34xx Lynnfield Series
Xeon 35xx Series
Xeon 55xx Series
Xeon 65xx Series
Xeon 75xx Series
i3-2100 Series
i3/i5 Clarkdale Series
Xeon 34xx Clarkdale Series
Xeon 36xx Series
Xeon 56xx Series
Xeon E7-2800 Series
Xeon E7-4800 Series
Xeon E7-8800 Series
Core i7-620LE
Xeon E3-1100 Series
Xeon E3-1200 Series
Xeon E5-1400 Series
Xeon E5-1600 Series
Xeon E5-2400 Series
Xeon E5-2600 Series
Xeon E5-4600 Series
i7-3600-QE
Xeon E3-1100-C-v2 Series
Xeon E3-1200-v2 Series
Xeon E5-1400-v2 Series
Xeon E5-2400-v2 Series
Xeon E5-2600-v2 Series
Xeon E3-1200-v3 Series*
i3-4300 Series*
i5-4500-TE Series*
i7-4700-EQ Series*
*Haswell CPU	EVC L0 Merom	EVC L1 Penryn	EVC L2 Nehalem	EVC L3 Westmere	EVC L4 Sandy Bridge	EVC L5 Ivy Bridge

Refer # Enhanced vMotion Compatibility (EVC) processor support (1003212) | VMware KB

[jadedpuppy]

Thanks for the response.  Quick follow up question though.  Why wouldn't we just increase the EVC level to Haswell on the existing cluster? Were you suggesting this to bypass the need for a full power off cycle of all the guests?

[RAJ_RAJ · Accepted solution]

Hi,

You can increase / decrease  the EVC level with below options .

Change the EVC Mode for a Cluster in the vSphere Web Client

Configure EVC to ensure that virtual machine migrations between hosts in the cluster do not fail because of CPU feature incompatibilities.

Several EVC approaches are available to ensure CPU compatibility:

■	If all the hosts in a cluster are compatible with a newer EVC mode, you can change the EVC mode of an existing EVC cluster.
■	You can enable EVC for a cluster that does not have EVC enabled.
■	You can raise the EVC mode to expose more CPU features.
■	You can lower the EVC mode to hide CPU features and increase compatibility.

Prerequisites

■	Verify that all hosts in the cluster have supported CPUs for the EVC mode you want to enable. See http://kb.vmware.com/kb/1003212for a list of supported CPUs.
■	Verify that all hosts in the cluster are connected and registered on vCenter Server. The cluster cannot contain a disconnected host.
■	Virtual machines must be in the following power states, depending on whether you raise or lower the EVC mode.

Refer # vSphere 5.5 Documentation Center

EVC Mode	Virtual Machine Power Action
Raise the EVC mode to a CPU baseline with more features.	Running virtual machines can remain powered on. New EVC mode features are not available to the virtual machines until they are powered off and powered back on again. A full power cycling is required. Rebooting the guest operating system or suspending and resuming the virtual machine is not sufficient.
Lower the EVC mode to a CPU baseline with fewer features.	Power off virtual machines if they are powered on and running at a higher EVC Mode than the one you intend to enable.

[jadedpuppy]

Ah, I misread that.  I thought you had to power down guests before raising the EVC level, but in reality you can raise whenever you want, but need to power the guests down after the EVC is raised in order for the guests to gain the new CPU architecture capabilities.  Thanks.

[RAJ_RAJ]

Mark my post as "helpful" or "correct" if I've helped resolve or answered your query!

[chalkynz]

Don’t forget the CPU is presented to guests, so Windows guests e.g. will detect new device and likely want a reboot.  After that should be able to move them around freely.