Virtual Machines and Hypervisors

Virtualization lets one physical server pretend to be many separate computers. Each pretend computer is a virtual machine (VM) with its own operating system, applications, virtual CPU, memory, and disk. The VMs share the real hardware underneath but stay isolated from each other.

This is the foundation of modern data centers and the cloud. Instead of one application per physical box, a single powerful server can host dozens of VMs, cutting cost, power use, and floor space dramatically.

A hypervisor (also called a Virtual Machine Monitor) is the software layer that creates and runs VMs. It carves up the physical CPU, RAM, and storage and hands slices to each VM, keeping them isolated so one crash cannot take down its neighbors.

The hypervisor schedules access to real hardware, just like an operating system schedules apps. To each guest OS, it looks like the VM owns a complete physical machine.

A Type 1 hypervisor runs directly on the hardware with no host operating system beneath it. Because it sits on bare metal, it is fast, efficient, and secure, making it the choice for production servers and clouds.

• VMware ESXi
• Microsoft Hyper-V
• KVM (Kernel-based Virtual Machine)
• Xen

Data centers run Type 1 hypervisors so a single host can serve many tenants at once.

A Type 2 hypervisor runs as an application on top of a normal operating system like Windows or macOS. It is easy to install and great for testing, learning, and desktops, but it is slower because requests pass through the host OS first.

• VMware Workstation and Fusion
• Oracle VirtualBox
• Parallels Desktop

Use Type 2 to run Linux on your laptop; use Type 1 to run a server farm.

The host is the physical machine and the hypervisor that runs everything. A guest OS is the operating system installed inside a VM. You can mix guests freely: a single host might run Windows Server, Ubuntu Linux, and an older Windows version side by side.

Each guest believes it has dedicated hardware, but all of them share the host pool of CPU and memory under the hypervisor schedule.

Admins assign each VM a share of vCPU (virtual processor cores), RAM, and disk. Overcommitting means assigning more total virtual resources than the host physically has, betting that not all VMs peak at once.

Done carefully this boosts efficiency; done carelessly it causes resource contention, where VMs fight for CPU or memory and slow down. Right-sizing each VM keeps performance predictable.

A snapshot captures a VM exact state at a moment in time. If a patch or change breaks something, you roll back to the snapshot in seconds. Cloning copies an entire VM to make an identical new one quickly.

These features make VMs far more flexible than physical servers, where rebuilding a broken box could take hours. Snapshots are not backups, though, since they live on the same host storage.

Containers (like Docker) are a lighter form of virtualization. Instead of a full guest OS each, containers share the host kernel and package only the app and its dependencies. They start in milliseconds and use far less memory.

VMs isolate at the hardware level with a full OS each; containers isolate at the OS level. Both are common, and many real deployments run containers inside VMs for layered isolation.

Live migration moves a running VM from one physical host to another with little or no downtime. The hypervisor copies the VM memory across the network to the new host, then switches over so seamlessly that users rarely notice.

This enables hardware maintenance, load balancing, and failover without shutting services down. VMware calls it vMotion; it is a key reason virtualized environments stay highly available.

Cloud providers run massive farms of hypervisors. When you rent a cloud server, you are really getting a VM on shared hardware. Virtualization lets the provider spin up your VM in minutes, scale it, and bill only for what you use.

For a network technician this matters because the network now extends inside the host, connecting virtual machines through virtual switches that you will meet in the next lesson.

Benefits: hardware consolidation, fast provisioning, easy backups via snapshots, isolation, and live migration for uptime.

Trade-offs: the hypervisor adds a small overhead, overcommitting risks contention, and many VMs on one host create a single point of failure if that host dies. Good design spreads critical VMs across multiple hosts to manage this risk.

Test your grasp of hypervisor types.

Virtualization splits one physical server into many isolated virtual machines, managed by a hypervisor. Type 1 hypervisors run on bare metal for production; Type 2 run on a host OS for desktops and testing. VMs each get vCPU, RAM, and disk, support snapshots, cloning, and live migration, and are the building block of cloud computing.