Virtualization

A complete learning path through VMs, hypervisors, virtual networks and storage, containers, security, and a safe hands-on lab.

3 technologies

Start here: Virtualization is the idea of turning physical computing resources into flexible, isolated environments. This guide connects the hardware, the hypervisor, virtual machines, containers, networks, storage, security, and a safe home lab.

Interactive diagram

Server virtualization layerVirtual devicesVirtual devicesVirtual devicesVirtual devicesSchedules and maps resourcesSchedules and maps resourcesGuest VM AGuest VM AGuest VM BGuest VM BType 1 hypervisorType 1 hypervisorPhysical server hardwarePhysical server hardware
Legend

Current step

Hardware provides a finite resource pool

The physical server supplies processor time, memory, storage, and network devices.

This is a teaching model. Some Type 1 platforms also use a privileged management partition or operating-system services; the key difference is where the virtualization layer sits.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

The big idea: one machine becomes a resource pool

Imagine a school lab with one powerful server and several classes that need different computers. Buying a separate physical server for every class would waste equipment, power, and space. Virtualization lets software divide one physical computer’s resources into separate environments that behave like independent machines.

The host still has a finite amount of CPU time, memory, storage, and network capacity. Virtualization does not create extra physical resources; it shares and manages what exists. A good design makes that sharing useful without allowing one workload to surprise or starve another.

The same principle appears beyond server VMs. Storage can be pooled into logical volumes, network switches can be virtual, and desktop environments can be delivered remotely. This page focuses on hardware and server virtualization, then shows how those ideas connect to containers and cloud platforms.

Vocabulary that makes the picture clear

Term Plain-language meaning
Host The physical computer, plus the software that manages its hardware.
Hypervisor or VMM The layer that creates VMs and mediates their access to hardware resources.
Virtual Machine (VM) A software-defined computer with virtual CPU, memory, storage, and devices.
Guest or Guest OS The operating system running inside a VM.
vCPU A virtual processor the guest can schedule work on; it is not automatically a dedicated physical core.
Virtual disk A disk presented to a guest and stored as a file, volume, or remote storage object.
vNIC A virtual network adapter connected to a virtual switch or network.
VM image A reusable file or template used to create a VM; its exact format depends on the platform.

Keep the roles separate in your mind: the host owns the physical resources, the hypervisor controls the virtual machines, and each guest uses its virtual hardware to run its own operating system and applications.

Interactive diagram

One VM · guest OS plus virtual devicesCompute requestsCompute requestsMemory viewMemory viewDisk I/ODisk I/ONetwork framesNetwork framesvm-vcpu ↔ vm-hypervisorvm-memory ↔ vm-hypervisorvm-disk ↔ vm-hypervisorvm-vnic ↔ vm-hypervisorPhysical resourcesPhysical resourcesGuest OS and appsGuest OS and appsvCPUvCPUGuest memoryGuest memoryVirtual diskVirtual diskvNICvNICHypervisorHypervisorPhysical hostPhysical host
Legend

Current step

The guest schedules work on vCPUs

A vCPU is a virtual scheduling context; it is not automatically one permanently reserved physical core.

The guest sees virtual devices, not a dedicated physical computer. The hypervisor schedules and maps requests to the host resources available to it.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

What happens when a guest runs a program

The guest operating system behaves as if it has a computer of its own. It schedules processes on its vCPUs, manages its memory, and sends disk or network requests to virtual devices. The virtualization platform maps those virtual resources onto physical resources and keeps the VM’s state isolated from other VMs.

Modern processors provide virtualization extensions that help a hypervisor run guest code efficiently while retaining control over sensitive operations. Memory virtualization translates between guest and host memory views. Storage and network requests pass through virtual devices and their backends. Some devices can use paravirtualized drivers to reduce overhead; others can be emulated for compatibility.

This is why a VM can often run close to native speed, but performance is never guaranteed by the word “virtual.” A busy host, slow storage, poor sizing, missing drivers, or a saturated network can still make a guest feel painfully slow.

Type 1 and Type 2 hypervisors

The common teaching model separates hypervisors into two types:

Type Where it runs Typical fit Examples
Type 1 On the hardware as the virtualization layer. A management operating system or partition may still provide device and management services. Server platforms, clusters, and production VM hosting. Microsoft Hyper-V, VMware ESXi, and KVM-based platforms.
Type 2 As an application on a conventional desktop operating system. Personal labs, demonstrations, and running another OS beside everyday apps. Oracle VirtualBox and VMware Workstation.

These labels are useful for a first mental model, but real implementations have more detail than a two-box chart suggests. For example, KVM is a Linux kernel virtualization facility commonly paired with QEMU and management tools. Hyper-V uses a hypervisor with a privileged root partition. Evaluate the full platform and its management model, not just its type label.

For a laptop lab, a hosted desktop hypervisor is usually the easiest start. For a server fleet, learn the platform’s cluster, access-control, storage, backup, and upgrade model before putting important workloads on it.

CPU virtualization, emulation, and nested VMs

Hardware-assisted virtualization features such as Intel VT-x and AMD-V help a hypervisor run guest operating systems while controlling privileged operations. Firmware settings may expose or disable those features. Some platforms also require second-level address translation support for particular capabilities.

Virtualization is not the same as emulation. A VM usually presents virtual hardware compatible with the guest CPU architecture, then uses hardware assistance where available. An emulator can model a different CPU or machine architecture in software; this offers flexibility but can be much slower. QEMU supports both system emulation and hardware-assisted accelerators such as KVM.

Nested virtualization means running a hypervisor inside a VM so that the guest can create its own VMs. It is useful for training and some CI or cloud scenarios, but it requires support through the physical processor, outer hypervisor, guest configuration, and sometimes the cloud provider. Do not assume it works everywhere.

Resource planning: CPU, memory, and NUMA

CPU

A vCPU is a scheduling opportunity, not a promise of one permanently reserved physical core. Assign enough vCPUs for the workload, then observe CPU ready time, host contention, and application latency using the platform’s own tools. Giving every VM far more vCPUs than it can use can make scheduling less predictable.

Memory

Guest memory must be backed by host memory or by a platform mechanism that manages memory pressure. Dynamic memory and overcommit features can increase density, but they do not remove the physical limit. If the host starts swapping heavily or reclaiming memory, several VMs may become slow at once. Leave headroom for the host and critical services.

NUMA and accelerator devices

Large servers group CPU cores and memory into NUMA nodes with different access costs. For high-performance workloads, virtual CPU and memory placement can matter. GPUs and other devices may be passed through or shared using platform-specific technologies, but passthrough changes portability and isolation trade-offs. Start with ordinary virtual devices unless the workload has a measured need.

Interactive diagram

Independent guest workloadsvCPU · memoryvCPU · memoryvCPU · memoryvCPU · memoryvCPU · memoryvCPU · memoryPhysical capacityPhysical capacityApplication VMApplication VMDatabase VMDatabase VMLab VMLab VMHypervisor schedulerHypervisor schedulerPhysical host resource poolPhysical host resource pool
Legend

Current step

Guests receive virtual capacity

The hypervisor presents vCPUs and memory to each guest while drawing on the same host pool.

Illustrative only: no capacity numbers are implied. Overcommit can increase density, but sustained demand beyond available host capacity can cause contention and poor performance.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Virtual disks, images, snapshots, and backups

A virtual disk can be stored in formats such as VDI, VHDX, VMDK, or QCOW2; support depends on the hypervisor. Thin-provisioned storage grows as data is written, while thick-provisioned storage reserves more capacity up front. Thin disks save initial space but can still fill the host when they grow, so monitor actual free capacity.

An image or template is a starting point for creating VMs. A clone is a copy of a VM or template, often used to create a separate environment. A snapshot or checkpoint records a point-in-time VM state, sometimes including disk state and memory depending on the product and options.

Critical rule: A snapshot is not an independent backup. Snapshot chains can consume storage, depend on the original virtual disk, and preserve mistakes or malware. Use a separate backup system, test restores, and delete snapshots according to the platform’s guidance.

Snapshots are useful before a short experiment or risky configuration change. They are not a long-term history system. For databases and other stateful applications, coordinate application consistency before capturing or restoring state.

Interactive diagram

Checkpoint relationshipCheckpoint relationshipCreate separate instanceCreate separate instanceCopy to separate systemCopy to separate systemSource VMSource VMSnapshot / checkpointSnapshot / checkpointCloneCloneIndependent backup storageIndependent backup storage
Legend

Current step

Use a snapshot for a short experiment

A checkpoint helps return one VM to an earlier state, but it is not an independent backup.

A snapshot may depend on the original virtual disk and can preserve unwanted state. A clone is a separate VM copy. An independent backup is designed for recovery even if the primary VM storage is lost.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Virtual switches and network modes

A VM’s virtual network adapter connects to a virtual switch or a provider’s virtual network. Common desktop modes include:

Mode What it usually allows Good for
NAT The guest makes outbound connections through the host; inbound access may require port forwarding. A first internet-connected lab with limited exposure.
Bridged The guest appears as a peer on the physical local network and may receive a LAN address. Testing services as another device on a trusted network.
Host-only The host and selected VMs communicate on a private network, usually without direct internet access. Isolated labs and host-to-guest administration.
Internal network Selected VMs communicate with each other without connecting to the host’s normal network. Multi-VM exercises that should remain contained.

Names and behavior vary between products. A virtual switch is not automatically a firewall: use firewall rules, network segmentation, and the narrowest connectivity needed. Bridged mode can expose a VM to other devices on the LAN, so do not use it casually for unknown or unpatched guests.

Interactive diagram

Guest traffic is translated by the hostOutboundOutboundnat-vm-b ↔ nat-switchnat-switch ↔ nat-hostnat-host ↔ nat-routernat-router ↔ nat-internetOutboundIPGuest VM AGuest VM AGuest VM BGuest VM BVirtual NATVirtual NATHost network stackHost network stackLAN routerLAN routerInternetInternet
Legend

Current step

NAT carries guest traffic outward

The guest sends through a virtual NAT service and the host network stack; return traffic is associated with that outbound flow.

Names and details vary by hypervisor. These are conceptual paths: choose the narrowest connectivity needed, and do not assume a virtual switch is a firewall.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Build your first VM safely

Use the official manual for the hypervisor you choose. This sequence is a mental checklist, not a replacement for product-specific instructions:

  1. Check the host. Confirm CPU virtualization support, available memory, free disk space, and whether firmware virtualization is enabled. Keep resources available for the host operating system.
  2. Install a trusted hypervisor. Download it only from its publisher and check the supported host and guest versions. Do not install random “VM images” from file-sharing sites.
  3. Download an operating-system image. Use the OS publisher’s official download page and verify checksums or signatures when provided.
  4. Create one VM. Give it a clear name, select the guest OS, and assign conservative CPU, memory, and disk resources. Start with NAT or an isolated network.
  5. Install and update the guest. Use the normal installer, apply updates, and create a standard user for daily work. Install guest integration tools only from the hypervisor’s official channel.
  6. Practice one reversible change. Take a short-lived snapshot, make a harmless configuration change, observe the result, and restore the snapshot.
  7. Clean up. Shut down the guest properly, remove lab-only resources when finished, and keep separate backups for any files you want to preserve.

VirtualBox’s official manual documents creating a VM and its snapshots. Windows Server administrators should use Microsoft’s Hyper-V documentation; Linux hosts can study KVM and QEMU documentation. Menus and defaults change between versions, so check the manual that matches your installed release.

Server virtualization: clusters, migration, and availability

In a data centre, a hypervisor platform may manage many hosts as a cluster. Live migration moves a running VM between compatible hosts with limited interruption, subject to the platform’s CPU, network, storage, and configuration requirements. High availability can restart or recover workloads after a host failure, but it does not prevent every outage or replace backups.

Administrators use resource pools, reservations, limits, monitoring, and placement rules to manage contention. A cluster still needs enough spare capacity to tolerate maintenance or a failed host. If every host is already full, a recovery plan exists only on paper.

Cloud infrastructure builds on these ideas but adds provider-managed networking, storage, identity, metering, and APIs. A cloud VM is still a VM from the learner’s perspective, but the provider controls much of the physical platform. Understand the shared-responsibility boundary before exposing services or storing important data.

A VM presents virtual hardware and normally runs its own guest kernel. A container is an isolated process environment that shares the host operating-system kernel. Container tools use operating-system isolation and resource controls, and package application files and dependencies into images.

Virtual Machine Container
Runs a guest OS and its own kernel. Runs isolated processes using the host kernel.
Usually uses more memory and storage per environment. Usually starts quickly and has less per-instance overhead.
Can run a different compatible guest OS kernel from the host. Must be compatible with the host kernel family and runtime.
Useful for OS labs, stronger workload boundaries, and legacy systems. Useful for packaging and repeatedly deploying application processes.

These are different boundaries with different risks, not a “secure versus insecure” switch. Containers can run inside VMs, and cloud platforms commonly use VMs to isolate groups of container workloads. Choose isolation, performance, portability, and operations together.

Interactive diagram

VM includes a guest OS and kernelContainers share the host kernelvm-hardware ↔ vm-hypervisorvm-hypervisor ↔ vm-guestvm-guest ↔ vm-appcontainer-hardware ↔ container-kernelcontainer-kernel ↔ container-runtimecontainer-runtime ↔ container-acontainer-runtime ↔ container-bPhysical hardwarePhysical hardwareHypervisorHypervisorVM · guest OS + kernelVM · guest OS + kernelApplicationApplicationPhysical hardwarePhysical hardwareHost OS kernelHost OS kernelContainer runtimeContainer runtimeContainer AContainer AContainer BContainer B
Legend

Current step

A VM virtualizes hardware

The hypervisor presents virtual devices and each VM runs its own guest OS and kernel.

Both approaches provide useful isolation, but at different layers and with different trade-offs. Containers can also run inside VMs, combining application packaging with a VM boundary.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Kubernetes is not a hypervisor

Kubernetes manages containerized workloads across a cluster. It schedules Pods onto nodes, checks declared state, and coordinates services and updates. A node may be a physical server or a VM. Kubernetes does not replace the hypervisor that virtualizes that server’s hardware.

Keep the layers straight: the hypervisor manages VMs; a container runtime runs containers; Kubernetes manages container workloads across nodes. Some specialized projects run VMs through Kubernetes, but that is an added capability, not what Kubernetes itself means.

Interactive diagram

VM-backed worker nodevirtual-hardware ↔ virtual-hypervisorvirtual-hypervisor ↔ virtual-workervirtual-worker ↔ virtual-runtimevirtual-runtime ↔ virtual-pod-avirtual-runtime ↔ virtual-pod-bSchedules workloadsSchedules workloadsvirtual-service ↔ virtual-pod-avirtual-service ↔ virtual-pod-bPhysical hostPhysical hostHypervisorHypervisorWorker node VMWorker node VMContainer runtimeContainer runtimePod APod APod BPod BKubernetes control planeKubernetes control planeServiceService
Legend

Current step

The hypervisor provides worker VMs

Physical hosts and a hypervisor sit below the Kubernetes worker node.

Kubernetes schedules and reconciles container workloads; it is not the hypervisor. A worker node may be a VM or a physical server, and the control plane manages workloads across nodes.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Where virtualization appears

  • Server virtualization: several server workloads share fewer physical hosts.
  • Desktop virtualization: centrally managed desktop environments are delivered to users.
  • Network virtualization: virtual switches, routers, overlays, and policy create logical networks.
  • Storage virtualization: physical storage is pooled and presented as logical volumes or services.
  • Application virtualization: applications run in separated or remotely delivered environments.
  • Operating-system-level virtualization: containers isolate processes while sharing a kernel.
  • Cloud IaaS: providers expose virtual compute, network, and storage through service APIs.

Virtualization is valuable when isolation, flexibility, repeatable environments, or consolidation solves a real problem. It also adds a management layer and consumes resources. A small, stable workload may be simpler on bare metal or a managed application service.

Security: isolation helps, but it is not magic

Treat the hypervisor and its management plane as critical infrastructure:

  • Keep the hypervisor, host OS, guest OSs, firmware, and guest integration tools supported and patched.
  • Restrict management interfaces to authorized administrators and a protected management network.
  • Use least privilege, strong authentication, and separate administrator accounts for routine work.
  • Segment VM networks and apply firewalls; do not assume two VMs are isolated just because they are virtual.
  • Build from trusted images, remove unused virtual devices, and protect secrets outside VM templates.
  • Protect snapshots and virtual disks as sensitive data; they may contain passwords, keys, or personal information.
  • Limit shared folders, clipboard sharing, USB passthrough, and other host-guest bridges to what the lab needs.
  • Back up important systems independently and test recovery.

NIST’s virtualization guidance describes hypervisor and virtual-network risks in detail. It is foundational guidance rather than a replacement for current product-specific security baselines.

Troubleshooting by symptom

Symptom First checks
VM will not start Confirm hardware virtualization support, firmware settings, available memory and disk, and hypervisor/host compatibility. Read the platform’s exact error before changing host security features.
Guest feels slow Check host CPU and memory pressure, vCPU sizing, storage latency, snapshots, guest updates, and virtual device drivers. Compare with host activity rather than guessing.
Guest has no network Inspect the virtual NIC connection, selected network mode, DHCP, guest firewall, host firewall, and port-forwarding rules. Test from guest to gateway before testing the internet.
Virtual disk will not grow Check host free space, thin-provisioned disk limits, snapshot chains, and whether the guest filesystem itself needs resizing.
A nested VM cannot start Verify support at every layer: physical CPU, outer hypervisor, VM configuration, guest hypervisor, and cloud provider policy.
A snapshot restore causes problems Confirm whether memory state was included, whether the VM has external state such as a database, and whether the snapshot chain is healthy. Prefer application-aware backups for important data.

Make one change at a time and record the original setting. Avoid disabling host security controls as a blind troubleshooting shortcut; use the official documentation for the exact hypervisor and error.

Mini project: a contained two-VM lab

Build a small lab that teaches both virtualization and boundaries:

  1. Create one Linux VM and one second VM from trusted OS images.
  2. Put both on an internal or host-only virtual network.
  3. Give each VM a clear role and modest resource allocation.
  4. Observe CPU, memory, disk, and network use on both the guests and host.
  5. Take a temporary snapshot, change a harmless setting, and restore it.
  6. Document which services can reach each VM and how you would back up the data you care about.

Do not expose an experimental service to the public internet. Keep the exercise on an isolated network, patch the guests, and delete lab resources when finished.

Glossary for the next lesson

Term Remember it as
Hypervisor / VMM The virtual-machine manager between workloads and physical resources.
Type 1 / Type 2 Hypervisor platform classifications based on how the virtualization layer is deployed.
vCPU / vRAM / vNIC Virtual CPU, memory, and network adapter presented to a guest.
Image / template A reusable starting point; platform formats and content vary.
Clone A separate copy created from a VM or template.
Snapshot / checkpoint A short-term point-in-time VM state, not an independent backup.
Live migration Moving a running VM between compatible hosts with limited interruption.
Passthrough Giving a VM direct access to a physical device, with portability and isolation trade-offs.
Nested virtualization Running a hypervisor inside a VM.
Overcommit Assigning more virtual capacity than the host can guarantee at the same time.

Trusted sources and further study

Use official documentation for the exact product version you install. Security settings, supported hardware, and user-interface steps change over time.

Explore the topic lessons