How many types of VMs are there?
There is no single official number. The count depends on how you classify virtual machines (VMs). The most useful approaches are by what the VM emulates, by the hypervisor that runs it, and by the instance family a cloud provider sells. Cloud providers typically organize their VMs into about five families: general purpose, compute optimized, memory optimized, storage optimized, and accelerated computing. Each family contains many sizes.
System VMs and process VMs
The broadest split comes from Smith and Nair (2005), who divide virtual machines into two groups:
- System virtual machines emulate a whole machine and run a full operating system. Guests on VMware ESXi, Microsoft Hyper-V, KVM, or Oracle VirtualBox are examples.
- Process virtual machines run a single program and stop when that program exits. The Java Virtual Machine and the .NET Common Language Runtime (CLR) are examples.
A process VM is not a hypervisor, and it does not run an operating system.
Type 1 and Type 2 hypervisors
System VMs are run by a hypervisor, which comes in two designs:
- Type 1 (bare-metal) hypervisors run directly on the hardware. Examples include VMware ESXi, Microsoft Hyper-V, Xen, and KVM.
- Type 2 (hosted) hypervisors run on top of an existing operating system. Examples include Oracle VirtualBox, VMware Workstation and Fusion, and Parallels Desktop.
Hyper-V and Azure also use Generation 1 (BIOS-based) and Generation 2 (UEFI-based) virtual machines. The generation determines the firmware and boot options the VM offers.
For the broader set of virtualization types, such as storage and network virtualization, see types of virtualization in cloud computing.
Cloud instance families
Cloud providers sell VMs as instance types grouped into families. The table below shows the usual five families with example naming from AWS, Azure, and Google Cloud. Naming schemes change often, so check the current documentation.
| Family | Typical use | AWS | Azure | Google Cloud |
|---|---|---|---|---|
| General purpose | Balanced CPU and memory for web apps, small databases, and development | M and T | D | E2, N2, N4, C4 |
| Compute optimized | CPU-heavy work such as batch processing | C | F | C2, H3 |
| Memory optimized | Large in-memory databases and caches | R and X | E and M | M3 |
| Storage optimized | High input and output workloads and large local storage | I and D | L | Z3 |
| Accelerated computing | GPU, FPGA, or AI chip workloads | P, G, Inf, and Trn | N | A3, G2 |
Azure’s B series, for burstable workloads, is a separate family that is not shown in the table.
Other VM types
Providers also offer several specialized types:
- High-performance computing (HPC) VMs are tuned for tightly coupled parallel workloads. Azure’s H series is one example.
- Burstable VMs give each vCPU a baseline share of CPU time and allow short bursts using accumulated credits. The AWS T family and Azure B series are examples. The vCPU article explains baselines in more detail.
- Dedicated hosts reserve a whole physical server for one customer. This can help with some licensing or compliance requirements.
VM types by how you buy them
Pricing models give another way to classify VMs:
- On-demand: pay for what you use, with no commitment.
- Reserved or committed use: commit to a term in exchange for a lower rate.
- Spot or preemptible: discounted capacity that the provider can reclaim with short notice.
- Dedicated host: a whole physical host reserved for you.
The provisioning article explains how these options fit into capacity planning.
Containers are not a type of VM
Containers package an application with its dependencies, but they share the host operating system’s kernel. They do not have their own guest operating system. In many cloud platforms, containers run inside VMs. The comparison of containers and virtual machines explains the difference in more detail.
Instance size is not instance type
A size such as “large” or “xlarge” is a variation within a family. It is not a fundamentally different kind of VM. Choosing a size mainly sets the vCPU and memory amounts, and the meaning of a vCPU count matters more than the size name.
Key takeaways
- No single count of VM types exists. The answer depends on how you classify them.
- Cloud providers typically group VMs into about five families, with sizes within each.
- Hypervisor type, VM type, and purchase model are three different ways of classifying the same VMs.