The virtual machine failed to become vsphere HA protected and HA may not attempt to restart if after a failure

[HassanAlKak88]

Hello,

Suddenly we faced the following message for a group of virtual machines "The virtual machine failed to become vsphere HA protected and HA may not attempt to restart if after a failure"

the below steps applied with no luck:

- Disable then Enable HA on cluster level

- Reconfigure for vSphere HA for all hosts (receive an error "Operation timed out")

- Restart Hosts

- Eject hosts from cluster then rejoin

- Disconnect hosts from vcenter then connect

- Remove FDM agent from hosts and reinstall again

also noting that there no problem with free space on servers.

please any suggestions ?

[MikeStoica]

What vCenter version you have?

[HassanAlKak88]

Version: 6.5.0  Build: 5318154 

[MikeStoica]

Have you increased the resources on those machines? Sometimes this points to lack of resources

[daphnissov]

You've tried the obvious, so at this point I'd say pull the logs from the host to inspect. Make note of times which you've disabled and re-enabled HA to catch the timeout/error.

[towerxu]

same issue here....

no reason make any senssence....

[daphnissov]

Same response as above. Pull logs and have a look.

[towerxu]

I found some reports:

The target host does not support the virtual machine's current hardware requirements.

To resolve CPU incompatibilities, use a cluster with Enhanced vMotion Compatibility (EVC) enabled. See KB article 1003212.

MOVBE is unsupported.

FMA3 is unsupported.

CPUID faulting is not supported.

Supervisor Mode Execution Protection (SMEP) is unsupported.

RDRAND is unsupported.

Instructions to read and write FS and GS base registers at any privilege level are unsupported.

Half-precision conversion instructions (F16C) are unsupported.

Fast string operations (Enhanced REP MOVSB/STOSB) are unsupported.

The host is reporting errors in its attempts to provide vSphere HA support.