Enable vSphere EVC on a Mixed-CPU Cluster for Predictable vMotion

Problem: vMotion blocked by CPU generation mismatch

A DRS/HA cluster with same-vendor hosts but different CPU generations will reject vMotion and initial placement when a VM requires instructions only present on newer processors. The useful takeaway is to mask the processors to a common CPU feature set with Enhanced vMotion Compatibility so vMotion and DRS placement become predictable across generations.

Desired outcome

Enable EVC on a vCenter-managed cluster so all hosts expose one consistent CPU baseline. VMs can be powered on and vMotioned between the oldest and newest host without CPU compatibility failures, and DRS can place workloads without generation constraints.

Prerequisites

• vCenter-managed cluster with hosts from a single CPU vendor. Intel and AMD cannot share an EVC baseline.
• Consistent virtualization and BIOS settings across hosts, including Intel VT-x/AMD-V and unrestricted guest execution where required.
• Capacity to evacuate or power off VMs if the baseline is raised. Raising EVC requires VMs to be powered off or migrated to hosts already at or above the new baseline.
• A tested change and rollback plan, and a maintenance window. EVC is a cluster-wide setting.

Inventory and baseline selection

Inventory host CPU models and the instruction sets required by workloads. In vSphere Client open each host, Summary, Hardware, CPU, and record model and stepping. Compare the list to the EVC baselines supported by your vCenter/ESXi release. Baseline names and availability vary by release and microcode.

Choose the lowest baseline that covers all hosts and still satisfies guest requirements. A lower baseline is less disruptive to apply and preserves broader compatibility, but it masks newer CPU instructions.

Example decision

Example: an Intel cluster with Xeon Gold 6248 and Xeon Platinum 8360Y. The oldest host supports an Intel Skylake baseline and the newest host supports newer baselines. Selecting the Skylake baseline exposes a common feature set to both hosts. Before choosing, validate that applications do not require instructions introduced after Skylake, such as specific encryption or vector extensions.

Apply EVC baseline

1. In vSphere Client connect to vCenter as a user with Cluster Administrator privileges. Navigate to Hosts and Clusters, select the cluster, and open Configure > VMware EVC.
2. Note the current mode. If EVC is disabled, click Edit and enable EVC for the vendor, then select the chosen baseline for . If EVC is already enabled, select a new baseline.
3. Confirm the change. Raising the baseline will prompt for VM power-off or migration. Lowering the baseline applies to new power-ons and vMotions but does not immediately change running VMs.
4. Allow the cluster to complete the configuration task and verify host power state remains as intended.

Risks: raising the baseline can make VMs ineligible to power on on hosts below the new baseline. Schedule the change when HA admission control can tolerate required evacuations.

Expected checks

• Cluster reports the intended EVC mode and baseline under Configure > VMware EVC.
• A test vMotion of a representative powered-on VM between the oldest and newest host completes without compatibility warnings.
• Power-cycle a test VM on the oldest host and inspect guest-visible CPU flags with OS tools to confirm the baseline is applied.
• Review vCenter Tasks & Events and host/VM logs for EVC, DRS, or vMotion errors after the change.

Recovery options

• If vMotion or power-on fails, lower the baseline to the previous value, disable EVC, or relocate VMs to hosts that are compatible with the current baseline.
• If feature loss is suspected, move workloads back to newer hosts and re-evaluate the baseline against application requirements.
• Document the baseline change and revalidate DRS recommendations and HA admission control.

Limitations

EVC masks newer CPU instructions. Do not mix CPU vendors in an EVC cluster. Baseline availability and naming vary by vCenter/ESXi release; verify against your exact release supported list before production changes. Changing EVC is cluster-wide and affects all hosts.