Virtualization Concepts and Hypervisors

What Is Virtualization?

Virtualization is the process of using software to create a simulated version of a physical computing resource—such as a server, storage device, or network switch. Instead of one physical machine running one operating system, virtualization allows a single physical machine to run several independent operating systems at the same time. Each simulated environment is called a virtual machine (VM).

Virtualization is the technical foundation of cloud computing. Every major cloud provider—AWS, Microsoft Azure, Google Cloud—runs customer workloads inside VMs on massive physical servers in data centers. Understanding how virtualization works is essential for anyone supporting IT systems or networking infrastructure.

The Hypervisor: The Engine of Virtualization

The software layer that creates and manages VMs is called a hypervisor (also called a Virtual Machine Monitor, or VMM). The hypervisor sits between the physical hardware and the guest operating systems. It allocates CPU cycles, RAM, storage, and network bandwidth to each VM, ensuring that no single VM can monopolize resources or crash another.

There are two main types of hypervisors.

Type 1 Hypervisor (Bare-Metal)

A Type 1 hypervisor installs directly on the physical hardware—there is no host operating system underneath it. Because it has direct access to hardware, Type 1 hypervisors are more efficient and are the standard choice in enterprise data centers and cloud environments.

Common examples include:

• VMware ESXi
• Microsoft Hyper-V (when installed as a standalone role on Windows Server)
• Xen (used by Amazon Web Services as part of its infrastructure)
• KVM (Kernel-based Virtual Machine, built into the Linux kernel)

Type 1 hypervisors are preferred for production servers because they offer lower overhead, better performance, and stronger isolation between VMs.

Type 2 Hypervisor (Hosted)

A Type 2 hypervisor runs on top of a conventional host operating system (such as Windows or macOS), just like any other application. The host OS talks to the hardware first; the hypervisor talks to the host OS.

Common examples include:

• Oracle VirtualBox (free and open-source; used in this course)
• VMware Workstation / VMware Fusion
• Parallels Desktop

Type 2 hypervisors are easier to install and are ideal for learning, development, and testing on a personal workstation. The trade-off is added latency because every hardware call passes through the host OS before reaching physical resources.

How VMs Share Physical Resources

When a hypervisor creates a VM, it assigns a portion of the physical machine's resources to that VM:

• CPU: The hypervisor schedules virtual CPUs (vCPUs) on the physical CPU cores. Multiple VMs take turns using the same physical cores.
• RAM: Each VM receives a defined amount of memory. That memory is reserved from the physical RAM pool.
• Storage: The hypervisor presents a virtual disk to the guest OS, which is typically stored as a single large file on the host's physical drive (for example, a `.vmdk` or `.vdi` file).
• Network: Each VM is given one or more virtual NICs (vNICs). The hypervisor connects these to the physical NIC through a virtual switch, allowing VMs to communicate with each other and with external networks.

The guest OS has no direct knowledge of the physical hardware. It believes it is running on real hardware; the hypervisor makes that illusion possible.

Snapshots vs. Backups

Two terms that are easy to confuse in virtualized environments are snapshot and backup.

A snapshot captures the exact state of a VM at a specific point in time—including RAM contents, disk state, and settings. Snapshots are fast to create and allow quick rollback if a change breaks something. However, snapshots are stored on the same physical disk as the VM and are not a substitute for a true backup.

A backup copies VM data to a separate location (a different drive, server, or cloud storage). Backups protect against hardware failure, ransomware, and disaster. Best practice is to maintain regular backups even when snapshots are in use.

Virtualization as the Foundation of Cloud Computing

Cloud providers use Type 1 hypervisors running on racks of physical servers to carve out thousands of VMs on demand. When you launch a virtual machine instance in AWS or Azure, you are renting a VM that lives on one of their physical servers, managed by their hypervisor. The key cloud concepts—scalability, multi-tenancy, rapid provisioning, and pay-per-use billing—are all made possible by virtualization.

Safety and Best Practices

• Electrical safety: When working inside physical servers that host hypervisors, always follow lockout/tagout (LOTO) procedures before opening the chassis. Wear appropriate PPE and discharge static with an anti-static wrist strap before touching components.
• Resource planning: Never allocate more RAM to VMs than the host physically has (overcommitment can cause VM crashes). Monitor CPU and RAM usage in Task Manager or the hypervisor console to avoid degrading host performance.
• Access control: Hypervisor management consoles provide root-level control over all VMs. Protect these interfaces with strong passwords and restrict access to authorized personnel only.
• Snapshot discipline: Delete outdated snapshots regularly; they consume significant disk space and can slow VM performance over time.