VM vs. Container Comparison Language
5 exercises — Master the English vocabulary for comparing virtual machines and containers: hypervisor types, kernel isolation mechanisms, trade-offs, and workload selection.
0 / 5 completed
Quick reference: VM vs. container vocabulary
- Type-1 hypervisor — bare-metal (ESXi, KVM, Hyper-V); Type-2 — hosted on an OS (VirtualBox, Parallels)
- Namespaces — what a container can see (PID, network, mount, UTS, user)
- cgroups — what a container can use (CPU, memory, I/O limits)
- VM advantage — hardware-level isolation, full OS, stronger security boundary
- Container advantage — millisecond startup, shared kernel, higher density per host
1 / 5
A cloud architect explains the company's infrastructure: "Our on-prem data centre runs VMware ESXi directly on bare metal. Azure also uses a Type-1 hypervisor underneath. Developer laptops run VMs through VMware Workstation or Parallels — those are Type-2."
What is the key difference between a Type-1 and a Type-2 hypervisor?
Type-1 runs on hardware; Type-2 runs on top of an OS — the key trade-off is performance vs. convenience.
A Type-1 (bare-metal) hypervisor (VMware ESXi, Microsoft Hyper-V, KVM, Xen) is installed directly on physical hardware. It manages CPU, memory, and I/O with minimal overhead and is used in production data centres and all major cloud providers' underlying infrastructure.
A Type-2 (hosted) hypervisor (VMware Workstation/Fusion, VirtualBox, Parallels) runs as an application on a conventional OS (Windows, macOS, Linux). The host OS introduces an additional layer of overhead but makes setup far simpler — hence its prevalence on developer workstations.
Key vocabulary:
• hypervisor — software that creates and manages virtual machines by abstracting physical hardware
• Type-1 hypervisor — bare-metal; runs directly on hardware; e.g., ESXi, Hyper-V, KVM
• Type-2 hypervisor — hosted; runs on a host OS; e.g., VirtualBox, Parallels, VMware Workstation
• guest OS — the operating system running inside a virtual machine
• virtualisation — the abstraction of physical hardware resources into isolated virtual environments
A Type-1 (bare-metal) hypervisor (VMware ESXi, Microsoft Hyper-V, KVM, Xen) is installed directly on physical hardware. It manages CPU, memory, and I/O with minimal overhead and is used in production data centres and all major cloud providers' underlying infrastructure.
A Type-2 (hosted) hypervisor (VMware Workstation/Fusion, VirtualBox, Parallels) runs as an application on a conventional OS (Windows, macOS, Linux). The host OS introduces an additional layer of overhead but makes setup far simpler — hence its prevalence on developer workstations.
Key vocabulary:
• hypervisor — software that creates and manages virtual machines by abstracting physical hardware
• Type-1 hypervisor — bare-metal; runs directly on hardware; e.g., ESXi, Hyper-V, KVM
• Type-2 hypervisor — hosted; runs on a host OS; e.g., VirtualBox, Parallels, VMware Workstation
• guest OS — the operating system running inside a virtual machine
• virtualisation — the abstraction of physical hardware resources into isolated virtual environments