The host does not have sufficient CPU resources to satisfy the reservation. The host host-XXX can not satisfy the requested CPU resources of XXXX MHz. (larger value) Available CPU resources on the host: XXXX MHz. (lesser value)
7.x
8.x
The vCenter Server uses outdated resource availability data cached from the host, which is significantly lower than the actual available capacity reported by the ESXi VMkernel.
Check the true available capacity on the ESXi host via SSH:
root@esxi#] vsish -e get /sched/groups/4/stats/capacity
Sample output:
[root@esxi:~] vsish -e get /sched/groups/4/stats/capacity
group-capacity {
cpu-reserved:0 MHz
cpu-unreserved:68300 MHz
mem-reserved:0 KB
mem-unreserved:242200232 KB
If the cpu-unreserved value is significantly higher than the value reported in the vCenter error message, the issue is synchronization, proceed to steps below to resolve
The synchronization issue can be resolved by forcing the host to re-register its resource state with the vCenter Server.
Reboot the target ESXi host
Note: This is the most effective method, as it clears all management agent states and forces a clean inventory refresh upon connection.
If a reboot is disruptive, an alternative is to Disconnect and Reconnect the host in the vSphere Client:
Right-click the host Connection > Disconnect.
Wait 60 seconds.
Right-click the host Connection > Connect.
Once the host status is green and connected re-attempt the VM operation.