Every virtual machine runs on a hypervisor, but not all hypervisors sit in the same place. The type 1 vs type 2 hypervisor split describes whether the hypervisor runs directly on the hardware or as an application on top of a normal operating system. The choice affects performance, security and what the setup is good for.
Before you start
- Read what virtualization is if hypervisors are new to you.
Type 1 hypervisors (bare metal)
A type 1 hypervisor is installed straight onto the server and controls the hardware itself. Guests talk to it with no general-purpose OS in between.
- Examples: VMware ESXi, Microsoft Hyper-V (the role installs beneath Windows), Xen, and KVM (built into the Linux kernel, which turns Linux itself into the hypervisor).
- Strengths: lowest overhead, direct hardware access, small attack surface, designed for 24/7 production.
- Typical use: data centres, VPS hosting, private clouds.
Type 2 hypervisors (hosted)
A type 2 hypervisor is an application running on a desktop OS such as Windows, macOS or Linux. The host OS manages hardware; the hypervisor asks it for resources.
- Examples: Oracle VirtualBox, VMware Workstation and Fusion, Parallels Desktop, QEMU without KVM.
- Strengths: easy to install, great for testing OS images, labs and running a second OS on a laptop.
- Weaknesses: extra layer adds overhead, and host OS updates or crashes take all guests down.
Type 1 vs type 2 hypervisor comparison
| Type 1 | Type 2 | |
|---|---|---|
| Runs on | Hardware directly | A host operating system |
| Performance | Near native | Lower, depends on host |
| Security | Smaller attack surface | Inherits host OS risks |
| Management | Remote web UI, CLI or panel | Desktop GUI |
| Best for | Production servers, VPS hosting | Development, labs, desktops |
Where KVM fits
KVM blurs the line: it is a kernel module, so a Linux machine running KVM is still a full Linux system, yet guests run with hardware assistance at near-native speed. It is generally classed as type 1, and it powers most Linux VPS platforms including those managed by Virtualizor, VirtFusion and Proxmox VE.
Which should you choose?
- Running VMs for customers or production apps: choose a type 1 hypervisor such as KVM or Proxmox VE.
- Testing on your workstation: a type 2 tool like VirtualBox is quicker to set up.
- Want neither? Rent a VPS and let the provider run the hypervisor.
Frequently asked questions
Is Hyper-V type 1 or type 2?
Type 1. When enabled, Hyper-V loads beneath Windows, and the Windows install itself becomes a privileged partition.
Is VirtualBox ever type 1?
No. VirtualBox always runs as an application on a host OS.
Can type 2 hypervisors use VT-x or AMD-V?
Yes. Modern type 2 hypervisors use hardware extensions too, which narrows the performance gap, but the host OS still sits in the path.