Virtualization / Guide

Virtual machines and hypervisors explained simply

What a virtual machine is, what a hypervisor does, the difference between type 1 and type 2, the essential vocabulary (vCPU, snapshot, VirtIO, passthrough…) and what to check on your hardware before you start.

Virtualization Guide Beginner Published October 20, 2026 Translated November 20, 2026 12 min read Version française
Server cooling fans in a data centre
Photo: Winston Chen on Unsplash

In plain words

A virtual machine (VM) is a computer simulated in software, running inside a real computer. The hypervisor is the software that builds these simulated computers and shares the real hardware between them. Think of a block of flats: the land and the foundations are the hardware, each flat is a VM with its own door and furniture (its operating system), and the hypervisor is the building manager who shares out water, electricity and space between the flats.

1. What is a virtual machine?

A VM behaves exactly like a computer: it boots, has a BIOS or UEFI, installs from an ISO image, and runs Windows, Linux or another system without knowing it is virtual. But all its components are simulated:

Component In a VM On the real machine
Processor vCPUs (virtual processors) A share of the real cores' computing time
Memory A fixed amount, for example 4 GB Taken from the machine's real memory
Disk A virtual disk A plain file (or a volume) on the real disk
Network card A virtual card Connected to the real network by a virtual switch
Screen, keyboard A console Shown in a window or a web page

Two very practical consequences:

  • a VM is isolated: if it crashes, gets infected or is misconfigured, the other VMs and the physical machine are not affected;
  • a VM is a file: you can copy it, back it up, move it to another machine or roll it back.

2. Basic vocabulary

Term Meaning
Host The physical machine, and the system that manages virtualisation
Guest The system installed in the VM
Hypervisor The software that creates the VMs and shares the hardware between them
vCPU A virtual processor given to a VM
ISO image A system's installation file, the equivalent of the DVD or USB stick

3. Type 1 and type 2: two families of hypervisors

Type 1 ("bare metal") Type 2 ("hosted")
Where it's installed Directly on the hardware, instead of a regular operating system As an application, on an existing Windows, macOS or Linux
Analogy The building is built to be rented out You sublet rooms in your own house
Performance Close to the physical machine Good, but shared with the machine's own system
Typical use Servers, homelabs, businesses Testing a system on your computer, development, learning
Examples Proxmox VE (KVM), VMware ESXi, Microsoft Hyper-V, XCP-ng (Xen) VirtualBox, VMware Workstation, VMware Fusion, Parallels Desktop

Two cases that blur the line

  • KVM is built into the Linux kernel: it turns Linux itself into a type 1 hypervisor. It's the engine behind Proxmox VE, and also behind virt-manager or GNOME Boxes on a Linux desktop.
  • Hyper-V is a type 1 hypervisor, even when enabled on Windows 11. Once Hyper-V is enabled, the hypervisor starts first, and Windows itself runs on top of it, in a privileged partition called the "root partition".

4. Concepts to learn next

Concept What it is What it's for
Snapshot The VM's state frozen at a point in time Rolling back after a failed update or a test
Clone A complete copy of a VM Duplicating a machine that's already configured
Template A reference VM, never started, that you clone Creating identical VMs in seconds
Overcommit Giving the VMs more vCPUs or memory than really exist Possible for the processor, risky for memory
Thin provisioning The virtual disk only takes up the space actually written Saving space; watch that the real disk doesn't fill up
Paravirtualised drivers Drivers that know they're in a VM: VirtIO (KVM, Proxmox), VMware Tools, Hyper-V integration services Much better disk and network performance
Guest agent A small service in the VM that talks to the hypervisor (QEMU Guest Agent, VMware Tools) Clean shutdown, showing the IP address, consistent backups
Passthrough Giving a VM direct access to a real device: graphics card, disk controller, network card Native performance; the device is then no longer shared
Live migration Moving a running VM from one server to another without stopping it Maintenance without downtime, in a cluster
High availability (HA) Automatic restart of VMs on another server after a failure Service continuity, in a cluster

A snapshot is not a backup

A snapshot is stored on the same disk as the VM: if that disk fails, the VM and its snapshots disappear together. A snapshot is for rolling back a few hours or days; no longer, because it slows the VM down and grows over time. For a real backup, see the 3-2-1 rule.

5. What your machine needs

Hardware virtualisation

All recent processors can accelerate virtualisation, but the feature is sometimes disabled in the BIOS or UEFI.

Feature Intel AMD Role
Processor virtualisation VT-x AMD-V (sometimes called "SVM Mode" in the BIOS) Essential for any modern hypervisor
Input/output virtualisation VT-d AMD-Vi (IOMMU) Needed for device passthrough

Checking that it's enabled

Windows: Task Manager > Performance > CPU, line Virtualization: Enabled.

Linux:

lscpu | grep -i virtuali

The output shows VT-x or AMD-V. If nothing is displayed, the feature is disabled in the BIOS or missing.

macOS: Macs with Apple silicon have built-in virtualisation (Apple's Virtualization framework), used by Parallels Desktop, VMware Fusion or UTM. It only virtualises systems built for ARM processors, such as Windows 11 ARM or ARM versions of Linux; a system for x86 processors can only be emulated there, very slowly.

Resources

  • Memory is almost always the first limit: each VM really reserves it. Add up the memory of all the VMs, plus 2 to 4 GB for the host.
  • Storage comes next: an SSD changes everything, because several VMs read and write at the same time.
  • The processor shares well: most VMs spend their time waiting. Don't give a single VM more vCPUs than the machine has logical cores.

6. Virtual disk formats

Each hypervisor has its own disk format. Conversion tools exist (qemu-img, for example), which lets you migrate a VM from one hypervisor to another.

Format Hypervisor Note
.qcow2 KVM, Proxmox VE QEMU's native format: snapshots, thin provisioning
.raw / .img KVM, Proxmox VE Raw image, the simplest and fastest
.vmdk VMware Also read by VirtualBox and Proxmox
.vhdx Hyper-V Successor to .vhd
.vdi VirtualBox VirtualBox's native format
.ova / .ovf All (exchange format) A complete packaged VM: configuration and disks

7. Virtual machine or container?

A VM simulates an entire computer, with its own system and its own kernel. A container (Docker, Podman, LXC) shares the host's kernel and only isolates the application: it starts in a second and uses far fewer resources, but it is less isolated and can only run systems compatible with the host's kernel (no Windows in a container on a Linux host, for example). The two complement each other: containers often run inside a VM. Example: rootless containers with Podman and Quadlet.

8. What it's for, in practice

  • Learning and testing risk-free: install a Windows Server, break a configuration, go back to the snapshot.
  • Consolidating several servers on a single physical machine: less hardware, lower power consumption.
  • Isolating: separating the file server, home automation and the web server, so that a problem on one doesn't affect the others.
  • Keeping an old system alive for old software that no longer runs on recent machines.
  • Building a homelab: see building your homelab: where to start.

Key points

  • A VM is a simulated computer; its disk is a file, which makes it easy to copy, back up and move.
  • The hypervisor shares the hardware between VMs. Type 1: directly on the hardware (Proxmox VE, ESXi, Hyper-V, XCP-ng). Type 2: as an application (VirtualBox, VMware Workstation).
  • Enable VT-x or AMD-V in the BIOS; VT-d or AMD-Vi for passthrough.
  • Memory is the first limit; install the paravirtualised drivers in every VM.
  • A snapshot is not a backup.

Read next