The vSphere Availability guide states “A slot is a logical representation of memory and CPU resources. By default, it is sized to satisfy the requirements for any powered-on virtual machine in the cluster.” - In simple terms a slot can be consumed by a single virtual machine, but a virtual machine may consume more than one slot.
Host Failures Cluster Tolerates: This is the default option. Interestingly, it's also probably the most misunderstood and incorrectly configured. First, while this setting is the default, it's not good enough as configured out of the box. This policy uses a calculation called 'slot size' to determine how many VMs can run on a given host.

If VM1 has 2GHZ and 1024GB reserved and VM2 has 1GHZ and 2048GB reserved the slot size for memory will be 2048MB+memory overhead and the slot size for CPU will be 2GHZ. Now how does HA calculate how many slots are available per host? Of course we need to know what the slot size for memory and CPU is first.

VMware vSphere is VMware's virtualization platform, which transforms data centers into aggregated computing infrastructures that include CPU, storage, and networking resources. vSphere manages these infrastructures as a unified operating environment, and provides you with the tools to administer the data centers that participate in that environment.

The two core components of vSphere are ESXi and vCenter Server. ESXi is the virtualization platform where you create and run virtual machines and virtual appliances. vCenter Server is the service through which you manage multiple hosts connected in a network and pool host resources.

Want to know what is in the current release of vSphere? Look at the latest vSphere release notes.

Learn About Some of Our Features

Beginning in vSphere 7.0, you can only deploy or upgrade to vCenter Server 7.0 using an appliance. The new vCenter Server appliance contains all the Platform Services Controller services from earlier releases, preserving all previous functionality, including authentication, certificate management, and licensing. All Platform Services Controller services are consolidated into vCenter Server, simplifying deployment and administration. As these services are now part of vCenter Server, they are no longer described as a part of Platform Services Controller.

vSphere 7.0 introduces vSphere Lifecycle Manager, a centralized and simplified lifecycle management mechanism for VMware ESXi 7.0 hosts. This new feature includes the functionality that Update Manager provided in previous vSphere releases. With vSphere Lifecycle Manager you can manage ESXi hosts by using images and baselines at the cluster level.

Learn how to use vSphere with Tanzu to transform vSphere into a platform for running Kubernetes workloads natively on the hypervisor layer. With this functionality, you can enable a vSphere cluster to run Kubernetes workloads by configuring it as a Supervisor Cluster. Within the Supervisor Cluster, you can create resource pools, called Supervisor Namespaces, and configure them with dedicated memory, storage, and CPU. You can directly deploy containers natively on ESXi within a Supervisor Namespace. These containers live within a special type of pod called a vSphere Pod. You can also leverage the Tanzu Kubernetes Grid Service to easily provision Kubernetes clusters that run within dedicated Supervisor Namespaces.

You can view available vCenter Server updates and upgrades and produce interoperability reports about VMware products associated with vCenter Server using Update Planner. You can also generate pre-update reports that let you make sure your system meets the minimum software and hardware requirements for a successful upgrade of vCenter Server. The report provides information about problems that might prevent the completion of a software upgrade, and actions you can take to remedy those problems.

You can use centralized license management to manage licenses for ESXi hosts, vCenter Server, vSAN clusters, and other VMware solutions. Learn how to use the VMware vSphere Client to manage licenses in your vCenter Server environment.

Learn how to configure networking for vSphere, including how to create vSphere distributed switches and vSphere standard switches, monitor networks to analyze the traffic between virtual machines (VMs) and hosts, and manage network resources. vSphere networking is one of the most critical components in your environment, as it is how your ESXi hosts and VMs communicate.

You can learn about vSphere storage to help you plan a storage strategy for your virtual data center. You can also learn how to configure and use the virtualized and software-defined storage technologies that ESXi and vCenter Server provide. vSphere supports several storage technologies for both traditional and software-defined storage environments.

Learn how to secure your environment using vSphere security features and best practices to safeguard your environment from attack. vSphere provides comprehensive, built-in security, delivering secure applications, infrastructure, data, and access.

You can provide business continuity using vCenter High Availability (vCenter HA) and vSphere Fault Tolerance (FT). vCenter HA provides failover protection against hardware and operating system outages within your virtualized IT environment. If there is a host failure, Fault Tolerance provides continuous protection for a VM.

You can use resource pools, clusters, vSphere Distributed Resource Scheduler (DRS), vSphere Distributed Power Management (DPM), and vSphere Storage I/O Control to manage and allocate resources for ESXi hosts and vCenter Server.

Try Our Deployment and Planning Tools

The following resources are designed to help you plan your vSphere data center deployment, and effectively manage your vSphere environment.

vSphere Hardware and Guest Operating System Compatibility Guides. An online reference that shows what hardware, converged systems, operating systems, third-party applications, and VMware products are compatible with a specific version of a VMware software product.
VMware Product Interoperability Matrices. Provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, vCenter Server, and other VMware products.
VMware Configuration Maximums. When you configure, deploy, and operate your virtual and physical equipment, you must stay at or below the maximums supported by your product. The limits presented in the Configuration Maximums tool are tested limits supported by VMware.

Access Developer and Automation Documentation

VMware {code} is a website dedicated to our developer and automation community. To learn about vSphere APIs, SDKs, and command-line interfaces, visit these VMware {code} resources:

VMware command-line interfaces under Automation Tools

Explore Our Videos

You can learn about deploying, managing, and administering vSphere by reading the documentation, and by watching videos on the VMware Information Experience video channel.

Learn More About vSphere

To learn about vSphere and data center virtualization, see the following resources.

Learn more about vSphere by visiting the vSphere Product Page.
Ask questions about vSphere by visiting the vSphere Community Forum. You can get help, opinions, and feedback from other VMware users by participating in the discussion forums.
Explore vSphere without having to install it using the VMware vSphere Hands-on Labs environment.
Learn about the solutions vSphere provides to help you overcome your IT struggles, and create a more efficient digital infrastructure by visiting vSphere White Papers and Technical Notes.
Read the latest products announcements, technical articles, and operations guidance from VMware on the vSphere Blog.
Learn about benchmarking, performance architectures, and other performance-focused topics at the blog VMware VROOM!, maintained by VMware's Performance Engineering team.
Visit the blog virtuallyGhetto by William Lam, a Staff Solutions Architect working at VMware. The blog focuses on automation, integration, and operation of the VMware Software Defined Datacenter (SDDC).

Use vSphere Documentation

The vSphere documents in HTML reflect the latest vSphere update release of each major vSphere version. For example, version 7.0 contains all the updates for 7.0.x releases. All our documentation comes in PDF format, which you can access by selecting the Download PDF icon on any page in the HTML documentation. PDFs for previous releases of vSphere are available for download in a ZIP archive format. The archive can be found under the Archive Packages heading for each major version in the table of contents on the left.

You can create custom documentation collections, containing only the content that meets your specific information needs, using MyLibrary.

I’ve been receiving a lot of questions around slot sizes lately. Although I point everyone to my HA Deepdive post not everyone seems to understand what I am trying to explain. The foremost reason is that most people need to be able to visualize it; which is tough with slot sizes. Just to freshen up an outtake from the article:

HA uses the highest CPU reservation of any given VM and the highest memory reservation of any given VM. If there is no reservation a default of 256Mhz will be used for the CPU slot and the memory overhead will be used for the memory slot!

If VM1 has 2GHZ and 1024GB reserved and VM2 has 1GHZ and 2048GB reserved the slot size for memory will be 2048MB+memory overhead and the slot size for CPU will be 2GHZ.

Now how does HA calculate how many slots are available per host?

Of course we need to know what the slot size for memory and CPU is first. Then we divide the total available CPU resources of a host by the CPU slot size and the total available Memory Resources of a host by the memory slot size. This leaves us with a slot size for both memory and CPU. The most restrictive number is the amount of slots for this host. If you have 25 CPU slots but only 5 memory slots the amount of available slots for this host will be 5.

Vsphere Slot Size Chart

The first question I got was around unbalanced clusters. Unbalanced would for instance be a cluster with 5 hosts of which one contains substantially more memory than the others. What would happen to the total amount of slots in a cluster of the following specs:

Five hosts, each host has 16GB of memory except for one host(esx5) which has recently been added and has 32GB of memory. One of the VMs in this cluster has 4CPUs and 4GB of memory, because there are no reservations set the memory overhead of 325MB is being used to calculate the memory slot sizes. (It’s more restrictive than the CPU slot size.)

This results in 50 slots for esx01, esx02, esx03 and esx04. However, esx05 will have 100 slots available. Although this sounds great admission control rules the host out with the most slots as it takes the worst case scenario into account. In other words; end result: 200 slot cluster.

With 5 hosts of 16GB, (5 x 50) – (1 x 50), the result would have been exactly the same. To make a long story short: balance your clusters when using admission control!

The second question I received this week was around limiting the slotsizes with the advanced options das.slotCpuInMHz and/or das.slotMemInMB. If you need to use a high reservation for either CPU or Memory these options could definitely be useful, there is however something that you need to know. Check this diagram and see if you spot the problem, the das.slotMemInMB has been set to 1024MB.

Notice that the memory slotsize has been set to 1024MB. VM24 has a 4GB reservation set. Because of this VM24 spans 4 slots. As you might have noticed none of the hosts has 4 slots left. Although in total there are enough slots available; they are scattered and HA might not be able to actually boot VM24. Keep in mind that admission control does not take scattering of slots into account. It does count 4 slots for VM24, but it will not verify the amount of available slots per host.

To make sure you will always have enough slots and know what your current situation is Alan Renouf wrote an excellent script. This script reports the following:

Vmware Slot Size Calculation

Example Output:

Vsphere Slot Size

Cluster : Production
TotalSlots : 32
UsedSlots : 10
AvailableSlots : 22
SlotNumvCPUs : 1
SlotCPUMHz : 256
SlotMemoryMB : 118

Vsphere Ha Slot Size

My article was a collaboration with Alan and I hope you find both article valuable. We’ve put a lot of time into making things as straight forward and simplistic as we possibly can.