Type 1 vs Type 2 Hypervisors
ESXi/Proxmox vs VirtualBox — production vs laptop.
Learning objectives
- Distinguish Type 1 (bare-metal) and Type 2 (hosted) hypervisors
- Match hypervisor type to use case: lab, production, desktop
- Place Proxmox VE and VMware ESXi on the type spectrum
Two families of hypervisors
A hypervisor is the layer that creates and runs VMs. How it sits relative to the physical hardware defines its type.
Type 1 — bare-metal
The hypervisor installs directly on the server hardware. No general-purpose host OS underneath (or a minimal one integrated into the product). VMs run as peers managed by the hypervisor.
- Examples: VMware ESXi, Proxmox VE (Debian-based but acts as appliance), Microsoft Hyper-V (Windows Server role), Xen
- Use when: Production servers, datacenters, Workshop Co.'s consolidated host in the Edmonton workshop
Type 2 — hosted
A normal desktop OS (Windows, macOS, Linux) runs first. You install hypervisor software on top as an application. VMs are processes under that OS.
- Examples: VirtualBox, VMware Workstation/Fusion, Parallels
- Use when: Learning, testing, running Linux on a Mac laptop, temporary labs
Type 1 = hypervisor is #1, closest to the metal. Type 2 = hypervisor is second, sitting on a full OS.
Comparison table
| Attribute | Type 1 | Type 2 |
|---|---|---|
| Performance | Near-native; direct hardware access | Extra OS layer adds overhead |
| Management | Web UI, APIs, clustering | Desktop app |
| Typical hardware | Dedicated server | Developer laptop |
| Boot order | Hypervisor boots first | macOS/Windows boots first |
| Workshop Co. prod? | Yes — Proxmox or ESXi | No — lab only |
Worked example — learning path for Workshop Co.
Marcus, Workshop Co.'s part-time admin, wants to practice before touching production:
- Week 1: Install VirtualBox on his MacBook. Create an Ubuntu VM. Learn SSH, disk resize, snapshots.
- Week 2: Install Proxmox VE on a spare mini PC (Type 1). Import lessons from VirtualBox — same virtio drivers, same cloud-init concepts.
- Week 3: Migrate Workshop Co.'s three workloads to Proxmox production host.
Proxmox VE technically runs on Debian Linux, which makes it a debated edge case. In practice it behaves as a Type 1 appliance: you do not use it as a general desktop, and VMs run under KVM/QEMU managed by Proxmox — not as apps you launch from a GNOME menu.
ESXi vs Proxmox at a glance
| VMware ESXi | Proxmox VE | |
|---|---|---|
| Cost | Free tier limited; licensing for enterprise features | Open source + optional subscription |
| Best for | Enterprises with VMware skill base | Small biz, homelab, budget-conscious Canadian hosts |
| Containers | Tanzu (separate product line) | Built-in LXC containers |
Try it yourself
For each scenario, choose Type 1, Type 2, or bare metal:
- Marcus tests a PostgreSQL upgrade on his laptop before Saturday maintenance
- Workshop Co. production hosting for
www.workshopco.ca - A video rendering workstation needing full GPU passthrough
Sample answers
- Type 2 (VirtualBox/UTM on laptop) — disposable test VM
- Type 1 (Proxmox) — production consolidation
- Bare metal — GPU passthrough adds complexity; dedicated OS often simpler
Check your understanding
- Can you run VirtualBox on the same machine that runs Proxmox production VMs?
- Why would Workshop Co. not run production on Marcus's MacBook?
Answers
- Technically on different machines yes; on Proxmox itself you would not install VirtualBox — Proxmox already is the hypervisor.
- Laptop is not always on, lacks ECC RAM and redundant storage, and Type 2 adds overhead and sleep/reboot disruption.