VM Power On Fails with "operation failed: Insufficient resources to satisfy configured failover level for vsphere HA"
search cancel

VM Power On Fails with "operation failed: Insufficient resources to satisfy configured failover level for vsphere HA"

book

Article ID: 301492

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When attempting to power on a VM in a 2-node cluster, the error "Insufficient resources to satisfy configured failover level for vSphere HA" occurs due to HA detecting only one host instead of two. (Affects Clusters with 2 or More Nodes)
  • Rebooting the hosts does not resolve the issue.
  •  Admission control host failover capacity is set to default (percentage-based) or overridden values, but the error persists.
  •  Error "All Shared datastores failed on the host" may be present, even though all datastores are connected.

 

/var/log/vmware/vpxd/vpxd.log 


[YYYY-MM-DDTHH:MM:SS] verbose vpxd[06497] [Originator@6876 sub=DAS opID=lodd0w3o-12915983-auto-7ou1c-h5:71483818-8-01] Failover resources check: clusterMem=765919, clusterCpu=112887, memUsed=557, cpuUsed=64, memAvailPercent=99, cpuAvailPercent=99, numHosts=1 PMemTotal=0, PMemUsed=0, PMemAvailPercent=0.
[YYYY-MM-DDTHH:MM:SS] verbose vpxd[06497] [Originator@6876 sub=cdrsPlmt opID=lodd0w3o-12915983-auto-7ou1c-h5:71483818-8-01] Vm [vim.VirtualMachine:vm-456378,vm_name] failed RpAdmission with N3Vim5Fault34InsufficientFailoverResourcesFault9ExceptionE(Fault cause: vim.fault.InsufficientFailoverResourcesFault)

Environment

  • VMware vCenter Server 7.0.x
  • VMware vCenter Server 8.0.x

Cause

vCenter ignores one of the hosts in the cluster, resulting in numHosts being detected as 1 instead of 2. This is due to an underlying issue where the host is being ignored, often related to datastore connectivity issues. (Affects Clusters with 2 or More Nodes)

/var/log/vmware/vpxd/vpxd.log 

[YYYY-MM-DDTHH:MM:SS] verbose vpxd[08555] [Originator@6876 sub=DAS opID=ClusterSnapshot-4887f48d] Ignoring host [vim.HostSystem:host-ID,XX.XX.XX.XX]: connected=true, dasState=connected
[YYYY-MM-DDTHH:MM:SS] verbose vpxd[08322] [Originator@6876 sub=DAS opID=ClusterSnapshot-3530c5e5] Ignoring host [vim.HostSystem:host-ID,XX.XX.XX.XX]: connected=true, dasState=connected
[YYYY-MM-DDTHH:MM:SS] verbose vpxd[07683] [Originator@6876 sub=DAS opID=ClusterSnapshot-23ea262e] Ignoring host [vim.HostSystem:host-ID,XX.XX.XX.XX]: connected=true, dasState=connected
[YYYY-MM-DDTHH:MM:SS] verbose vpxd[06428] [Originator@6876 sub=DAS opID=ClusterSnapshot-46e1f5de] Ignoring host [vim.HostSystem:host-ID,XX.XX.XX.XX]: connected=true, dasState=connected

Resolution

1. Remove and re-add the problematic host to vCenter.
2. After re-adding the host, verify that numHosts is detected as 2, and the VM can be powered on without the "Insufficient resources" error.