Can any one please provide me a fix or solution for the below issue., while re-adding a host into the cluster getting below error. both the articles not useful in my case. Removed the host from the vCenter and tried to re-add it no luck.
we are using vSphere 6.5u1 on the host and Host is "HP BL460 Gen8" Sandy Bridge Generation. Other hosts in the cluster with same generation working. The effected host recently replaced with the mother board.
Error : 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.
The effected host recently replaced with the mother board.
The BIOS chipset is on the mainboard. So I think that a BIOS settings is different now. Maybe because of a newer BIOS version or in the past you have changed something that is no longer configured after the BIOS factory reset (maybe Intel VT or AMD-V settings or something similar).
I therefore recommend checking all BIOS settings between the hosts.
Check if the following VMware KB article helps:VMware Knowledge Base
Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.
Depending on which vCenter Server version/build you are using, EVC may expect the new CPU instruction that came with the latest CPU Microcode patches.
What you may do - that's what I did on customer environments that I'm maintaining - is to update the host's BIOS to the latest available version (https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=5177951&swItemId=MTX_6b168690b6b343b7bc3743...), to see whether this allows the host to join the cluster. You may also consider to patch the hosts to ESXi 6.5 Update 1g (7967591) if Update 2 is not an option for you yet (due to backup issues ...).
you can disable it simply and add the host.
That's not a good idea. If EVC complaints about an incompatibility, one should take this serious. Otherwise you risk issues with vMotion, or even guest OS crashes.
To resolve this issue:
Please consider marking this answer "CORRECT" or "Helpful" if you think your question have been answered correctly.
Can you check the BIOS setting MONITOR/MWAIT between the hosts?
Seen this "problem" now a couple of times. For sure the meltdown/spectre bios patches together with updated EVC modes are the trigger of the problem. We always fix it by creating a new cluster and moving the hosts into it followed by most of the VMs by performing a vMotion. At the end we often have a couple of VMs which cant be vMotion'd and we have to shutdown these VMs to move them.
IIRC, there is something in the release notes when the vCenter comes with the updated EVC modes.