Alarm "vSphere HA virtual machine failover failed" occurred - vSphere ESXi
search cancel

Alarm "vSphere HA virtual machine failover failed" occurred - vSphere ESXi

book

Article ID: 428321

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Virtual machine status is "disconnected" due to failover failure with the following error on vSphere Client :
    vSphere HA failover operation in progress in cluster #### in datacenter Datacenter: 0 VMs being restarted, 1 VMs waiting for a retry, 0 VMs waiting for resources, 0 inaccessible vSAN VMs

  • In the /var/log/fdm.log file, entries similar to the following are observed :
    YYYY-MM-DDTHH:MM:ss.SSSZ [#### verbose 'Placement' opID=####] [PlacementManagerImpl::HandleNotPlacedVms] Reset Vm /vmfs/volumes/####/vm/vm.vmx, vim.fault.NoCompatibleHost

Environment

VMware vSphere ESXi 8.0
VMware vSphere ESXi 7.0

Cause

A VM-Host affinity rule is configured with the specific requirement "Must run on hosts in group". vSphere HA respects these mandatory rules.
Due to this rule, Primary HA ESXi host cannot find a compatible ESXi host for the virtual machine when the ESXi host fails, preventing a successful failover.

Resolution

To resolve this issue, perform one of the following options: 

 Option 1. Relax the Affinity rule
      Change the VM-Host affinity rule from "Must run on hosts in group" to "Should run on hosts in group" (Soft Affinity). 
      This allows vSphere HA to violate the rule if the preferred hosts are unavailable.

 Option 2. Expand the Host Group
      Add additional healthy ESXi hosts to the Host Group associated with the mandatory affinity rule. 
      This ensures there are available resources satisfying the "Must" condition during a failure.


Checklist for HA Failover Readiness

Before troubleshooting individual virtual machine failover errors, ensure your cluster environment meets these baseline requirements to avoid FDM agent timeouts:

  • Audit VM Snapshot Count:

    • Check for excessive snapshot chains on the affected VM. A high number of snapshots (e.g., >20) can induce significant I/O latency during disk locking.
    • Action: If a large chain exists, consolidate snapshots to reduce VM "stun" time and storage overhead.
  • Verify NTP Stratum Status:

    • Ensure all ESXi hosts in the cluster are synchronized with a reliable NTP source.
    • Action: Verify that the NTP stratum level is low (ideally 1–3). High stratum levels can lead to clock drift and synchronization failures between the FDM agent and vCenter.
  • Verify Host BIOS/Firmware Compliance:

    • Ensure the host servers are running the latest vendor-recommended BIOS and firmware.
    • Action: Check the hardware vendor's support matrix (e.g., Dell PowerEdge, HPE ProLiant) to confirm your current version is compliant with the installed version of vSphere. Outdated firmware is a frequent cause of unexpected resource management instability.
  • Review VMkernel Storage Latency:

    • Check the VMkernel logs (/var/log/vmkernel.log) for storage latency warnings.
    • Action: If worst-case latency exceeds 200ms, investigate the storage backend for congestion before initiating further failover tests.



Additional Information

vSphere HA and DRS Affinity Rules