Skip to content
Calcrivo

VMware HA Capacity Calculator

Check vSphere HA admission control: how much capacity a percentage or N+1 slot policy reserves and whether restarts actually fit.

Inputs

hosts
GHz
GiB
%
VMs
MHz
GiB
%

Spare Cluster Capacity

50.1%

Reserve Demanded by Policy

12.5%

VMs to Restart After Failure

20VMs

CPU Headroom After Reserve

438.4GHz

Memory Headroom After Reserve

1,449.0GiB

Admission Control Verdict

Failover capacity is sufficient with room to power on more VMs

Step by step

  1. Values used

    Hosts in cluster = 8 hosts; CPU capacity per host = 83.20 GHz; Memory per host = 512 GiB; ESXi host memory overhead = 6 %; Powered-on VMs = 160 VMs; Average CPU demand per VM = 900 MHz; Average memory per VM = 12 GiB; Admission control policy = Slot policy — tolerate 1 host failure (N+1); Percentage reserved (percentage policy) = 25 %

  2. VMware HA Capacity

    reserve = failover hosts ÷ total hosts; restart demand = ceil(VMs ÷ hosts) × failover hosts × average VM demand, which must fit in cluster capacity minus current demand.

  3. Spare Cluster Capacity

    = 50.1

  4. Reserve Demanded by Policy

    = 12.5

  5. VMs to Restart After Failure

    = 20 VMs

  6. CPU Headroom After Reserve

    = 438.4 GHz

  7. Memory Headroom After Reserve

    = 1,449.0 GiB

  8. Admission Control Verdict

    = Failover capacity is sufficient with room to power on more VMs

How it works

Admission control reserves capacity in one of two shapes: a flat percentage of cluster CPU and memory, or slots sized so that losing N hosts still leaves room. Both reduce to the same test — cluster capacity minus current demand must exceed the demand of the VMs that were running on the hosts you are prepared to lose, checked separately for CPU and for memory. HA that cannot restart a host's worth of VMs is a false sense of safety, and the failure is silent until the day a host dies; equally, an over-generous reserve blocks legitimate power-on operations with an insufficient-resources error.

Formula

VMware HA Capacity

reserve = failover hosts ÷ total hosts; restart demand = ceil(VMs ÷ hosts) × failover hosts × average VM demand, which must fit in cluster capacity minus current demand.

failover hosts
Hosts whose workload must be absorbed by the survivors
reserve
Fraction of the cluster admission control holds back
restart demand
CPU and memory needed to power the failed host's VMs back on

Frequently Asked Questions

How is VMware HA Capacity calculated?

reserve = failover hosts ÷ total hosts; restart demand = ceil(VMs ÷ hosts) × failover hosts × average VM demand, which must fit in cluster capacity minus current demand. Admission control reserves capacity in one of two shapes: a flat percentage of cluster CPU and memory, or slots sized so that losing N hosts still leaves room. Both reduce to the same test — cluster capacity minus current demand must exceed the demand of the VMs that were running on the hosts you are prepared to lose, checked separately for CPU and for memory.

Why does VMware HA Capacity matter?

HA that cannot restart a host's worth of VMs is a false sense of safety, and the failure is silent until the day a host dies; equally, an over-generous reserve blocks legitimate power-on operations with an insufficient-resources error.

What values do I need to enter?

This calculator takes 9 inputs: Hosts in cluster, CPU capacity per host, Memory per host, ESXi host memory overhead, Powered-on VMs, Average CPU demand per VM, Average memory per VM, Admission control policy, Percentage reserved (percentage policy). The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Why should the reserve be sized against the largest host?

With mixed hardware, a percentage reserve calculated from the cluster average is too small when the biggest host fails. Size the reserve so the single largest host's workload fits, then convert that back into a percentage.

You might also need