• Vmware Ha Slot Size Calculations Calculator
• Vsphere Ha Slot Size Calculation
• Vmware Ha Slot Size Calculation
• Vmware Ha Slot Size Calculations Chart

Most readers probably know that VMware High Availability (or VMware HA) is the feature of VMware Infrastructure 3 that allows for virtual machines (VMs) to be rebooted on another available host in the event of an unexpected host failure. In these types of scenarios, a physical host goes down unexpectedly, typically due to hardware failure, and with it go a bunch of VMs. With VMware HA, these downed VMs will reboot on a different physical server in the HA cluster, thus minimizing downtime.

I had always considered that the “failover capacity,” i.e., how the number of VMs that could be supported in an HA cluster with a failed host, was calculated by VMware HA in an intelligent fashion similar to that used by VMware Distributed Resource Scheduling (VMware DRS). In other words, VMware HA would look at the needs of the downed VM, consider what is available across the various hosts, and then place virtual workloads accordingly. Sadly, that is not the case.

Once your slot size has been determined, the number of slots on each host in the cluster is counted. The lower resource determines their limit - so if a host can fit 100x the CPU slot size in terms of CPU resource, but can only fit 30x the memory limit, the host has 30 slots. That number is added up for each host in the cluster. This post clarifies more on the Total Slots, Used Slots & Available slots in VMware HA Slot calculation. I strongly recommend to read my previous post on HA slot calculation to fully understand the concepts of this post. From the above snapshot, Total Slots in Cluster = 234.

This article, titled HA Failover Capacity, by a VMware technical support engineer—“VMwarewolf”—provides more detailed information on how failover capacity is actually calculated. What actually happens is that VMware HA calculates a number of “slots” based on the least amount of RAM installed in a server in the cluster divided by the most amount of RAM configured for any VM in the cluster. In the article, the example is given of a server that has 16GB with at least one VM that is configured for 2GB of memory. That would create 8 slots (16GB / 2GB = 8 slots) for VMware HA.

That in and of itself is bad enough, since not all VMs will require 2GB, but here’s where it gets worse. After calculating the number of “slots” available on the smallest server in the cluster, it then extrapolates the total number of slots in the cluster using the number from that smallest server. So if one server in the HA cluster has 16GB but the remaining three have 64GB, all four servers will be treated as having only 16GB for the purposes of calculating HA “slots”. So, instead of the three bigger servers coming up with 32 slots, they’ll show up as having 8 slots. Ouch!

Be sure to keep this in mind when creating VMware HA clusters and planning for fault tolerance.

Vmware Ha Slot Size Calculations Calculator

Vsphere Ha Slot Size Calculation

Also, if you aren’t reading VMwarewolf’s stuff, you may want to start. He (or perhaps she?) is posting some good stuff.

Metadata and Navigation

Be social and share this post!

Vmware Ha Slot Size Calculation

Related Posts

Vmware Ha Slot Size Calculations Chart

• Troubleshooting VMware HA Isolation Response5 Oct 2007
• ESX Server and the Native VLAN13 Nov 2007
• Using scponly on ESX Server23 Oct 2007