Virtualization lets one physical computer act like several separate computers. Think of it like an apartment building. Instead of one family living in a giant mansion, a contractor divides the space into multiple apartments, each with its own kitchen, bathroom, and living area. Each family can live independently without interfering with the others, even though they all share the same foundation and structure.

In the world of computing, the software that acts as this contractor is called a hypervisor.

Also known as a virtual machine monitor (VMM), the hypervisor is the key ingredient that makes virtualization possible. It sits between the physical hardware and the virtual machines, acting as a traffic cop. It separates the computer's resources—like the CPU, memory, and storage—and provides each virtual machine with its own slice.

This setup allows you to run different operating systems on the same machine. You could have a Windows machine running a virtual instance of Linux to test software, or a single powerful server in a data center running dozens of virtual servers for different customers.

Hypervisors come in two main varieties, each with a different approach to managing this process.

The primary distinction between hypervisors comes down to where they live in the computer's software stack: do they run directly on the hardware, or do they run on top of an existing operating system?

This direct access to the physical hardware makes Type 1 hypervisors extremely efficient and secure. They are the standard for enterprise-level applications and cloud computing, where performance and stability are critical.

Common examples include:

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

Because they run within an operating system, Type 2 hypervisors are simpler to set up and manage. This makes them ideal for individual users, developers, and testers who need to run different operating systems on their personal computers without dedicating an entire machine to the task.

Examples you might have used include:

• Oracle VirtualBox
• VMware Workstation/Fusion
• Parallels Desktop

The tradeoff for this convenience is a slight performance penalty. Since the hypervisor's requests for hardware resources must pass through the host operating system first, there's an extra layer of translation that can slow things down compared to a bare-metal setup.

Whether running directly on hardware or as an application, hypervisors are the fundamental technology that enables the efficiency and flexibility of virtualization.