Imagine you have a physical server with 8 CPU cores, 64 GB of RAM, and 2 TB of storage.
You install one operating system on it. That OS runs one application.
Your server uses about 15% of its CPU and 20% of its RAM.
The rest sits idle.
Figure 1 – Without virtualization
This is the problem that virtualization solves.
The Role of the Hypervisor
A hypervisor is the software layer that creates and manages virtual machines (VMs).
It sits between the physical hardware and the VMs, dividing the real resources into virtual ones.Each VM gets its own virtual CPU (vCPU), virtual RAM (vRAM), and virtual disk (vDisk).
From the VM’s perspective, it looks and behaves like a standalone physical machine.
Figure 2 – Hypervisor creates VMs
You can run a Linux web server and a Windows database on the same physical hardware.
The VMs are completely isolated from each other.
If one VM crashes, the others keep running.Two Types of Hypervisors
Not all hypervisors work the same way.
The key difference is where the hypervisor sits relative to the hardware.
There are two types, and each one targets a different use case.Answer the question below
What does a hypervisor create and manage?
A Type 1 hypervisor installs directly on the physical hardware.
There is no host operating system underneath.
The hypervisor itself becomes the OS of the server.Direct Access to Hardware
With Type 1, your VMs communicate with the hypervisor.
The hypervisor then communicates directly with the CPU, RAM, and storage. There is no extra layer in between.
Figure 3 – Type 1 bare-metal architecture
This direct access means near-native performance.
Your VMs run almost as fast as if they had the hardware to themselves.Common Type 1 Hypervisors
The most common Type 1 hypervisors are:
VMware ESXi – the industry standard in enterprise data centers
Microsoft Hyper-V – integrated into Windows Server
KVM – open-source, built into the Linux kernel
All three share the same principle: the hypervisor owns the hardware, and your VMs run on top of it.
Answer the question below
Does a Type 1 hypervisor require a host OS underneath it?
A Type 2 hypervisor does not install directly on the hardware.
It runs on top of a host operating system, just like any other application on your computer.But why would you add an extra layer between your VMs and the hardware?
Because you still need your laptop for daily work.
You want to browse the web, write emails, and run VMs at the same time.The Extra Layer
With Type 2, your VMs go through the hypervisor, then through the host OS, and finally reach the hardware.
That extra layer introduces additional overhead.
Figure 4 – Type 2 hosted architecture
Your host OS consumes CPU and RAM for its own processes.
Your VMs compete with the host OS and your other applications for resources.Common Type 2 Hypervisors
The most common Type 2 hypervisors are:
Oracle VirtualBox – free and open-source, runs on Windows, macOS, and Linux
VMware Workstation – for Windows and Linux desktops
VMware Fusion – for macOS
This is the model you use when you run a virtual lab on your laptop.
Tools like GNS3, EVE-NG or Cisco Modeling Labs (CML) often run inside a VM on a Type 2 hypervisor.
You keep your Windows or macOS for daily work, and your VMs run alongside your browser and other apps.Answer the question below
Does a Type 2 hypervisor run directly on the hardware or on a host OS?
The key difference is the number of layers between your VM and the physical hardware.
Side-by-Side Architecture
Type 1 has three layers: hardware, hypervisor, VMs.
Type 2 has four layers: hardware, host OS, hypervisor, VMs.
Figure 5 – Type 1 vs Type 2 side by side
That extra host OS layer in Type 2 is where the performance difference comes from.
Your host OS consumes resources and adds latency between your VM and the hardware.
Type 1 eliminates that layer entirely.
Your hypervisor talks to the hardware without any intermediary.Answer the question below
Which type delivers better performance: Type 1 or Type 2?
When to Use Each Type
So how do you choose between them?
If your server’s only purpose is to host VMs, use Type 1.
You get maximum performance and you dedicate all resources to your virtual machines.
If you need your machine for daily work and also want VMs for labs or testing, use Type 2.
You keep your host OS and run VMs alongside your regular applications.Comparison Table
The table below summarizes the key differences between both types:
Feature
Type 1 (bare-metal)
Type 2 (hosted)
Installs on
Bare hardware
Host OS
Performance
Near-native
Overhead from host OS
Use case
Data center, production
Lab, development, personal
Examples
ESXi, Hyper-V, KVM
VirtualBox, Workstation, Fusion
Host OS required
No
Yes
Table 1 - Hypervisor: Type 1 vs. Type 2
Answer the question below
Which hypervisor type is best suited for a production data center?