VMware Cloud Community
VPXA
Enthusiast
Enthusiast

Enhanced vMotion Compatibility mode

Hi All,

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.

Reply
0 Kudos
15 Replies
Devi94
Hot Shot
Hot Shot

Do you have same hardware model for all esxi hosts in cluster ?

Reply
0 Kudos
VPXA
Enthusiast
Enthusiast

Yes,

All are HP BL 460 Gen8 8 Cores

Reply
0 Kudos
sk84
Expert
Expert

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.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
Reply
0 Kudos
diegodco31
Leadership
Leadership

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.

Diego Oliveira
LinkedIn: http://www.linkedin.com/in/dcodiego
Reply
0 Kudos
Devi94
Hot Shot
Hot Shot

If all your hosts come with same CPU model, why do you need EVC to be enabled ? you can disable it simply and add the host.

Reply
0 Kudos
a_p_
Leadership
Leadership

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 ...).

André

Reply
0 Kudos
a_p_
Leadership
Leadership

Devi94

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.


André

Reply
0 Kudos
HassanAlKak88
Expert
Expert

Hello,

To resolve this issue:

  1. Enter the BIOS setup (F9 on most systems at boot).
  2. Select Advanced Options.
  3. Select Processor Options.
  4. Change No-Execute Memory Protection to Enabled, if necessary.
  5. Change Intel Virtualization Technology to Enabled, if necessary.
  6. Reboot the host.
  7. Enable EVC in the cluster settings.

Please consider marking this answer "CORRECT" or "Helpful" if you think your question have been answered correctly.

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak


If my reply was helpful, I kindly ask you to like it and mark it as a solution

Regards,
Hassan Alkak
Reply
0 Kudos
VPXA
Enthusiast
Enthusiast

Thanks for your inputs Hassan, all the suggested options already enabled no luck.

Reply
0 Kudos
VPXA
Enthusiast
Enthusiast

Yes we are running with the same bios (I31) version.

Reply
0 Kudos
VPXA
Enthusiast
Enthusiast

Reply
0 Kudos
SupreetK
Commander
Commander

Can you attempt to re-add the host to the cluster and collect the vpxd.log as soon as the operation fails?

Cheers,

Supreet

Reply
0 Kudos
RickVerstegen
Expert
Expert

Can you check the BIOS setting MONITOR/MWAIT between the hosts?

Was I helpful? Give a kudo for appreciation!
Blog: https://rickverstegen84.wordpress.com/
Twitter: https://twitter.com/verstegenrick
Reply
0 Kudos
IRIX201110141
Champion
Champion

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.

Regards,

Joerg

Reply
0 Kudos
VPXA
Enthusiast
Enthusiast

Yes meltdown/spectre are updated with EVC for this we need to install the "cpu-microcode" patches, where the issue will be fixed. For us after installing the ESXi650-201806402-BG resolved the issue.

Reply
0 Kudos