About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Enhanced vMotion Compatibility (EVC) makes every host in a cluster present the same CPU feature set, so VMs can move between older and newer servers from the same CPU vendor. vCenter refuses to enable or raise EVC for one of two reasons. Either VMs that are already running use CPU features the chosen mode would hide ("Powered-on or suspended virtual machines on the host may be using CPU features hidden by that mode"), or a host's CPU or BIOS does not offer features the mode needs ("The host CPU lacks features required by that mode", as shown in KB 405881). The first is fixed by power-cycling the named VMs; the second by choosing a lower mode, changing a BIOS setting or updating ESXi.
What the error means
A VM picks up its CPU features at power-on and keeps them until it is powered off. The TechDocs page on VM EVC modes: "The EVC mode of a virtual machine is determined when the virtual machine powers on." It does not change "until it is powered off and powered on again."
So a VM started on a newer host without EVC can be using instructions that an older baseline hides. vCenter will not take those away from a running VM, and it refuses the change instead:
The host cannot be admitted to the cluster's current Enhanced vMotion Compatibility mode. Powered-on or suspended virtual machines on the host may be using CPU features hidden by that mode.
KB 421013 shows the message followed by the host's FQDN, and KB 411077 says the check "will point out which hosts contain VMs which are preventing the operation", so you can see which host holds the blocking VMs. It happens even "in the cluster with the same CPU model": the cause is "One or more VMs on this host have inherited CPU features higher to the EVC mode."
The second message is about the host, not its VMs. KB 405881 shows it in the vCenter UI:
The host's CPU hardware does not support the cluster's current Enhanced vMotion Compatibility mode. The host CPU lacks features required by that mode
Likely causes
| Cause | What you see | Where it is documented |
|---|---|---|
| Running VMs with features above the mode | "may be using CPU features hidden by that mode", host named | KB 421013, TechDocs |
| Per-VM EVC set on some VMs | Same message | KB 411077 |
| vCenter VM runs in the same cluster | Same message; a powered-on vCenter VM in the cluster blocks EVC | KB 411077, KB 324552 |
| Ice Lake hosts, VMs at hardware version 16 or later | "AVX512VPOPCNTDQ is unsupported." | KB 316465 |
| CPU feature off in BIOS | "AES instructions (AES-NI) are unsupported or disabled in the BIOS." | KB 396229, TechDocs requirements |
| Mode newer than ESXi supports | "EVCAdmissionFailed: the CPU family/model doesn't support this mode." | KB 405881 (Sapphire Rapids before 8.0 U1) |
| Mode above the oldest host's CPU | "The host CPU lacks features required by that mode" | KB 405881 (message); TechDocs requirements and KB 318962 (choosing a mode) |
Prove the cause before changing anything
All of these checks are read-only.
1. Read the whole message and note the host. The enable dialog lists each host that fails and why. KB 411077: "When attempting to enable cluster level EVC it will point out which hosts contain VMs which are preventing the operation."
2. List every VM's current EVC mode. KB 421013: "In Cluster > VMs tab, expand Manage Columns and select EVC CPU Mode". Then: "Check if any VMs lack an EVC Mode entry or are configured with an EVC Mode higher than the target value." TechDocs explains the blanks: for a powered-on VM outside an EVC cluster without per-VM EVC, the column "displays the EVC mode of the parent host", and "If per-VM EVC is deactivated, the EVC CPU Mode column for the virtual machine is empty" when the VM is off. KB 316465 adds that some affected VMs show nothing at all ("MinRequiredEVCModeKey is blank"), so an empty cell on a running VM is a candidate, not a clear.
3. Look for per-VM EVC. In each candidate VM's Edit Settings > VM Options > General Options, the VMware EVC section shows whether it is enabled (KB 446114). KB 411077: "Per-VM EVC may cause issues with enabling cluster level EVC."
4. Find where vCenter runs. If the vCenter VM is in this cluster and powered on, KB 411077 says that "will prevent enabling of EVC."
5. If the message is about the host CPU, read vpxd.log. On the vCenter appliance, /var/log/vmware/vpxd.log records the check. KB 405881 shows Running EVC test on esxi-1_fqdn with evcMode intel-sapphirerapids,vsga-baseline followed by EVCAdmissionFailed: the CPU family/model doesn't support this mode. KB 316465 shows the VM case as vim.fault.EVCAdmissionFailedVmActive with key = "cpuid.avx512vpopcntdq". The FAQ (KB 313545): "The missing features will be reported by the UI or in the vpxd log file."
6. Check the host requirements. TechDocs lists: "ESXi6.7 or later", the host connected to vCenter, CPUs from "A single vendor, either AMD or Intel.", and these BIOS features if available: "Hardware virtualization support (AMD-V or Intel VT)", "AMD No eXecute(NX)", "Intel eXecute Disable (XD)". "If you cannot enable EVC on a system with a compatible processor, ensure that all features are enabled in the BIOS."
7. Pick the right mode. KB 318962: in the Broadcom Compatibility Guide "select the CPU Series", select "Enhanced vMotion Capability Modes", and "Determine the Lowest Common CPU feature compatible on all ESXi hosts in the cluster."
Example (illustrative): cluster prod-a has two older hosts and one newer host, esx03, added last year. Enabling the older hosts' baseline fails, naming esx03. The EVC CPU Mode column shows three VMs on esx03 with the newer host's mode; every other VM shows the older mode. vCenter runs on another cluster. Those three VMs are the whole cause.
Fix
Running VMs above the mode. This is the TechDocs procedure: "Power off all the virtual machines on the hosts with feature sets greater than the EVC mode." Then "Click the Configure tab, select VMware EVC, and click Edit." and "Enable EVC for the CPU vendor and feature set appropriate for the hosts in the cluster, and click OK." Then power the VMs back on. Disruptive step: each named VM is powered off. A guest restart is not enough. KB 313545: "A warm reboot of the guest operating system is not sufficient to update the VMs EVC mode." The requirements page also allows "You can also migrate these virtual machines out of the cluster."
To find the blockers when the list is unclear, KB 421013 suggests: "Migrate VMs on <ESXi-Host-FQDN> one by one and enable EVC mode to observe whether the host triggering the error changes."
Per-VM EVC. KB 411077: "Power off and disable per-VM EVC on VMs that the cluster is calling issues with." Disruptive step: VM power-off.
vCenter in the same cluster. KB 411077: "you must create a new cluster with EVC enabled first, then migrate VM's to that new cluster." KB 324552 gives the steps: create the cluster with the EVC baseline, "Migrate all virtual machines from one of the ESXi hosts in the existing cluster. Put the host into Maintenance Mode. Drag and drop the ESXi host into the EVC cluster." Its prerequisites include "install the exact same version of ESXi on all hosts" and "Ensure the vCenter VM is connected to a Standard Switch or Ephemeral port group before migration". Risk: "VMware does not recommend using these steps for a vCenter Server virtual machine that is running on a Virtual Distributed Switch (VDS)." For a vSAN cluster, KB 411077 says to follow the separate vSAN procedure it links.
Ice Lake and hardware version 16 or later. KB 316465: identify powered-on VMs at hardware version 16 or later without per-VM EVC, "Perform a scheduled maintenance window to shut down these virtual machines", enable the baseline, then "Power on the virtual machines." Risk: it "requires downtime on the virtual machines."
BIOS feature off. KB 396229: "Proceed to engage the hardware support to enable the AES-NI feature in the ESXi host BIOS." Disruptive step: a BIOS change needs the host in maintenance mode and a reboot.
ESXi too old for the mode. KB 405881: "Upgrade the ESXi hosts to 8.0U1 or above"; "vCenter needs to be on 8.0U1 and above."
Mode above the oldest host. Choose the highest mode all hosts support. Lowering an existing mode needs VMs off: "Power off virtual machines if they are powered on and running at a higher EVC mode than the one you intend to enable." Risk: "If you take a snapshot of a running virtual machine before an EVC downgrade, an attempt to revert to that snapshot after the EVC downgrade fails and the virtual machine is left in a suspended state."
Raising the mode later is gentler. "Running virtual machines can remain powered on", but new features need "A full power cycling". The TechDocs change page notes the vmx.reboot.powerCycle parameter, set to TRUE, makes a guest reboot do that power cycle once.
Confirm the fix
- Configure > VMware EVC shows the mode as enabled for the cluster.
- Every host in the cluster shows as compatible, with no warnings.
- The EVC CPU Mode column shows the cluster mode, or a lower one, for every running VM.
- A test vMotion between the oldest and newest hosts succeeds.
What to watch afterwards
- New hosts. KB 318962: "The ESXi host should be added while in maintenance mode." Add hosts at the cluster's mode, not the reverse.
- New VMs started elsewhere. A VM powered on outside the cluster may carry more features than the cluster mode. KB 313545 warns it "may not be able to be vMotioned to the EVC cluster".
- Hardware refresh. When the oldest host retires, raise the mode and plan power cycles to pick up the new features.
- Hardware version upgrades. Higher VM hardware versions can expose more CPU features, as KB 316465 shows.
Read next
Related articles you may want next.
- VMwarevMotion fails: telling CPU compatibility, device dependencies and the vMotion network apartvMotion failing after adding a host or changing networks? Classify the error, test the vmkernel path with vmkping, find device blockers and plan EVC safely.Read article
- CloudHow to build and validate a VMware private-cloud clusterConfigure a three-host vSphere cluster and prove its placement, migration and recovery assumptions.Read article
- VMwarePlanning a VM Hardware Version Upgrade in vSphere: When, How and What to CheckVM hardware version upgrades are one-way. Check host and vCenter support, Tools first, backup or snapshot, then upgrade and verify the guest's devices and network.Read article
Risks and limits
- Enabling EVC with blocking VMs always costs downtime for those VMs; migrating them away is the only no-outage route, and only when another cluster can run them.
- Moving the vCenter VM between clusters can cut its network if its port group is not reachable on the new host; follow KB 324552's switch and port group checks.
- The EVC level tables and CPU lists change with each release; check the Broadcom Compatibility Guide for your exact CPUs and version.
NetLeverage runs its own hosting on VMware vSphere, vCenter and ESXi. Talk to an engineer.
Sources
- How Do You Activate vSphere EVC on an Existing Cluster — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- How to Determine the EVC Mode of Your Virtual Machine — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- Enhanced vMotion Compatibility Requirements for Hosts — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- Change the EVC Mode for a Cluster — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- Enable EVC failed on same CPU model cluster with error "The host cannot be admitted to the cluster's current Enhanced vMotion Compatibility mode." (KB 421013) — Broadcom, Updated On 03-04-2026, accessed 17 November 2026
- Can't enable cluster EVC - "Powered-on or suspended virtual machines on the host may be using CPU features hidden by that mode" (KB 411077) — Broadcom, Updated On 02-03-2026, accessed 17 November 2026
- Enable EVC in vCenter Server 6.5/6.7/7.0/8.0 if VC VM is part of the same cluster (KB 324552) — Broadcom, Updated On 07-31-2026, accessed 17 November 2026
- Unable to Enable Intel Ice Lake EVC Mode on vSphere Cluster Due to AVX512VPOPCNTDQ Feature Conflicts (KB 316465) — Broadcom, Updated On 10-26-2026, accessed 17 November 2026
- ERROR : EVCAdmissionFailed: the CPU family/model doesn't support this mode. When setting EVC mode of the cluster to Intel® "Sapphire Rapids" Generation (KB 405881) — Broadcom, Updated On 01-18-2026, accessed 17 November 2026
- AES instructions (AES-NI) are unsupported or disabled in the BIOS (KB 396229) — Broadcom, Updated On 05-19-2025, accessed 17 November 2026
- VMware EVC and CPU Compatibility FAQ (KB 313545) — Broadcom, Updated On 10-15-2026, accessed 17 November 2026
- ERROR: The target host does not support the virtual machine’s current hardware requirements. (KB 318962) — Broadcom, Updated On 09-16-2026, accessed 17 November 2026
- How to Configure Per-VM Enhanced vMotion Compatibility in vSphere 8.0 (KB 446114) — Broadcom, Updated On 06-29-2026, accessed 17 November 2026
This article was originally published on .