vSphere HA Slot Policy Practice: Slot Size and Failover Capacity
Free vSphere HA slot policy practice for the VCP-DCV (2V0-21.23). Each invented cluster gives the host resources and the VM reservations: work out the slot size, the slots per host and the Current Failover Capacity, and Check my answer names the slip, such as rounding up, using the average reservation or failing the smallest host first.
Hosts: available for VMs
VMs: reservations and overhead
Host figures are the CPU and memory available for VMs (the host's root resource pool), not its physical totals.
Every cluster is invented. Each VM here needs one slot, which is the default when no slot size option is set.
Practise the exams
Start with the free real exam questions for your exam, then get the full pack.
vSphere HA slot policy FAQ
The slot policy rules in short
- CPU slot: the largest CPU reservation of a powered-on VM. No reservation counts as 32 MHz.
- Memory slot: the largest memory reservation plus memory overhead of a powered-on VM.
- Slots per host: host CPU ÷ CPU slot and host memory ÷ memory slot, each rounded down. The smaller one wins.
- Current Failover Capacity: how many hosts, largest first, can fail with enough slots left for every powered-on VM.
- Available slots: slots left without the tolerated host failures, minus the used slots.
-
das.slotcpuinmhzanddas.slotmeminmb: an upper bound for the CPU or memory part of the slot.
How is the vSphere HA slot size calculated?
The slot has a CPU part and a memory part. The CPU part is the largest CPU reservation of any powered-on VM. The memory part is the largest memory reservation plus memory overhead of any powered-on VM. Powered-off VMs do not count.
What is the slot size when a VM has no reservation?
A VM with no CPU reservation counts as 32 MHz, the default of das.vmcpuminmhz. There is no default for the memory reservation (das.vmmemoryminmb defaults to 0 MB), so a VM with no memory reservation counts as its memory overhead alone.
How many slots does a host have?
Divide the CPU the host has available for VMs by the CPU slot size and round down. Do the same for memory. The smaller of the two numbers is the slots the host supports. In the Broadcom example, a host with 9 GHz and 6 GB and a slot of 2 GHz and 2 GB supports 3 slots, the smaller of 4 and 3.
What is the Current Failover Capacity?
It is how many hosts can fail, starting from the largest, and still leave enough slots for every powered-on VM. In the Broadcom example the hosts hold 4, 3 and 3 slots for 5 VMs: without the largest host 6 slots remain, which is enough, and without the two largest only 3 remain, so the Current Failover Capacity is 1.
How many slots are available?
Take the slots left without the hosts the cluster is set to tolerate losing, then subtract the used slots. In the Broadcom example, with Host failures cluster tolerates set to 1, the 6 slots on the two remaining hosts minus the 5 used slots leave 1 available slot.
What do das.slotcpuinmhz and das.slotmeminmb do?
Each sets an upper bound for one part of the slot. The CPU slot becomes the smaller of das.slotcpuinmhz and the largest CPU reservation. The memory slot becomes the smaller of das.slotmeminmb and the largest memory reservation plus overhead. They stop one VM with a much larger reservation from distorting the slot size.
What happens to a VM that is bigger than the capped slot?
Broadcom says VMs might require multiple slots when a fixed or maximum slot size is set. The saved pages do not give the exact count, so the upper bound step in this drill asks for the slot size only.
When does admission control block an operation?
When the Current Failover Capacity is less than the Configured Failover Capacity, the number of host failures you set the cluster to tolerate.
Which host figures does vSphere HA use?
The CPU and memory in the host's root resource pool, shown on the host's Summary tab, not the physical totals. Only hosts that are connected, not in maintenance mode and free of vSphere HA errors are counted.
Is the slot policy on the VCP-DCV exam?
Objective 4.6 of the VMware vSphere 8.x Professional (2V0-21.23) exam guide is "Create and configure VMware HA and DRS advanced options (Admission Control, Proactive HA, etc.)". The slot policy is one of the vSphere HA admission control policies.
Sources
- Broadcom TechDocs, VMware vSphere 8.0, vSphere Availability: Slot Policy Admission Control: how the slot size is calculated, the 32 MHz default, slots per host rounded down with the smaller number used, the Current Failover Capacity starting from the largest host, and the worked example with hosts H1 to H3 and VM1 to VM5.
- Broadcom TechDocs, VMware vSphere 8.0, vSphere Availability: vSphere HA Advanced Options: das.slotcpuinmhz and das.slotmeminmb as the maximum bound on the slot size, das.vmcpuminmhz (default 32 MHz) and das.vmmemoryminmb (default 0 MB).
- Broadcom: VMware vSphere 8.x Professional (2V0-21.23) exam guide: objective 4.6, Create and configure VMware HA and DRS advanced options (Admission Control, Proactive HA, etc.).
- Checked 20 November 2026. The tool's own approach: every cluster is invented, with 5 hosts and 5 VMs; each cluster gives the same answer whether the hosts are ranked by slots, CPU or memory, because the page does not define the largest host further; anything the pages do not state is left out. The drill reproduces the Broadcom worked example, and an independent re-solver agreed with it on 33,000 generated problems.
Checked 20 November 2026 against the Broadcom TechDocs pages for VMware vSphere 8.0 and the VMware vSphere 8.x Professional exam guide.
- DrillAWS IAM policy evaluation practiceDecide if a request is allowed or denied across identity policies, bucket policies, SCPs and permissions boundaries, and pick what decides it.
- CalculatorRAID calculatorUsable capacity and how many drive failures RAID 0, 1, 5, 6 and 10 survive.
- DrillServiceNow ACL practiceDecide if a read or write is granted and tap the ACL that decides it.