Resolving The Problem

Short Description

The following message is reported in the vCenter UI:

The host';s CPU hardware should support the cluster';s current Enhanced vMotion Compatibility mode, but some of the necessary CPU features are missing from the host. Check the host';s BIOS configuration to ensure that no necessary features are disabled (such as XD, VT, AES, or PCLMULQDQ for Intel, or NX for AMD). For more information, see KB article 1003212.

What';s Happening

The host cannot be added to the existing cluster because vCenter cannot detect some required CPU features.

Why it';s Happening

A review of the vCenter';s vpxd.log revealed that three specific CPU features are not detected. Namely:

cpuid.IBPB
cpuid.IBRS
cpuid.STIBP

Snippet of the log:

2019-02-11T20:00:28.572-06:00 info vpxd[7FEB5A5CB700] [user@example sub=Default opID=HostMigrationActionCommand-apply-6538905-ngc:70178628-fd] [VpxLRO] -- ERROR task-956840 -- domain-c25423 -- vim.ClusterComputeResource.moveInto: vim.fault.EVCAdmissionFailedCPUFeaturesForMode:
--> Result:
--> (vim.fault.EVCAdmissionFailedCPUFeaturesForMode) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> productName = <unset>,
--> productVersion = <unset>,
--> faults = (vmodl.MethodFault) [
--> (vim.fault.FeatureRequirementsNotMet) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> featureRequirement = (vim.vm.FeatureRequirement) [
--> (vim.vm.FeatureRequirement) {
--> key = "cpuid.IBPB",
--> featureName = "cpuid.IBPB",
--> value = "Bool:Min:1"
--> },
--> (vim.vm.FeatureRequirement) {
--> key = "cpuid.IBRS",
--> featureName = "cpuid.IBRS",
--> value = "Bool:Min:1"
--> },
--> (vim.vm.FeatureRequirement) {
--> key = "cpuid.STIBP",
--> featureName = "cpuid.STIBP",
--> value = "Bool:Min:1"
--> }
--> ],
--> vm = <unset>,
--> host = ';vim.HostSystem:ha-host';
--> msg = "The target host does not support the virtual machine';s current hardware requirements."
--> }
--> ],
--> currentEVCModeKey = ""
--> msg = "The host';s CPU hardware should support the cluster';s current Enhanced vMotion Compatibility mode, but some of the necessary CPU features are missing from the host. Check the host';s BIOS configuration to ensure that no necessary features are disabled (such as XD, VT, AES, or PCLMULQDQ for Intel, or NX for AMD). For more information, see KB articles 1003212 and 1034926."
--> }

How to Fix

1. Check the config file on the host being added to see if the specific features are detected by running the following command:

cat etc/vmware/config | grep -iE ';IBPB|IBRS|STIBP';

Expected output:

featMask.evc.cpuid.IBPB = "Val:1"
featMask.evc.cpuid.IBRS = "Val:1"
featMask.evc.cpuid.STIBP = "Val:1"

2. If nothing is returned, then re-install the specific VMware VIBs that related to these cpu-microcode.

a. Identify the currently installed cpu-microcode VIB version

esxcli software vib list | grep cpu

Example output:

cpu-microcode 6.5.0-2.57.9298722 VMware VMwareCertified 2019-02-07

b. Remove the cpu-microde VIB

localcli software vib remove -n cpu-microcode

c. Reboot the host to complete the VIB removal

or

e. Reboot the host for the change to take effect

3. Verify that the CPU features are found now

cat etc/vmware/config | grep -iE ';IBPB|IBRS|STIBP';

4. Retry adding the host in the cluster.

Related URL:

Enhanced vMotion Compatibility https://kb.vmware.com/s/article/1003212

vMotion/EVC incompatibility issues due to AES/PCLMULQDQ https://kb.vmware.com/s/article/1034926