com.vmware.vim.vmfeature.misc.rrsba_nocom.vmware.vim.vpxd.vmcheck.featureRequirementsNotMet.useClusterOrPerVmEvc
vpxd.log, you may see entries similar to: CompatCheck results: (vim.vm.check.Result) [ (vim.vm.check.Result) { vm = 'vm-####', host = 'host-####', error = (vmodl.MethodFault) [ (vim.fault.FeatureRequirementsNotMet) { faultMessage = [ (vmodl.LocalizableMessage) { key = "com.vmware.vim.vmfeature.misc.rrsba_no" } ... ] } ] } ]Virtual machines using Hardware Version 21 enable the RRSBA_NO (Restricted RSB Alternate) feature by default to advertise guest vulnerability status and prevent migration from non-vulnerable to vulnerable hosts.
Intel Sapphire/Emerald Rapids processors do not support this specific feature in the same way Ice Lake does. Because migration between different CPU generations is not guaranteed without Enhanced vMotion Compatibility (EVC), the compatibility check fails to prevent potential guest instability.
To resolve this issue, you must enable Intel Ice Lake EVC Mode at the cluster level. This creates a common CPU baseline that allows VMs to move seamlessly between Ice Lake and Emerald Rapids hosts.
Note: If you cannot power off all VMs at the cluster level, you may consider Per-VM EVC, though Cluster-level EVC is the recommended best practice for mixed-generation clusters.