1.8 Virtualization Fundamentals
Modern infrastructure abstracts software from hardware. This module covers hypervisor architectures, virtual networking logic, and the critical differences between VMs and containers.
Hypervisor Architectures
Type 1 (Bare-Metal)
- ArchitectureThe hypervisor is installed directly on the physical hardware, replacing a traditional operating system.
- AdvantageExtremely efficient, secure, and offers direct access to physical CPU and RAM resources.
- Real-World ExamplesVMware ESXi, Microsoft Hyper-V, Proxmox VE (KVM).
Enterprise data centers and MSP client servers.
Type 2 (Hosted)
- ArchitectureThe hypervisor is installed on top of an existing 'Host' Operating System (like Windows 11 or macOS).
- AdvantageEasy to install for testing, development, and building home-labs without dedicating an entire physical machine.
- Real-World ExamplesOracle VirtualBox, VMware Workstation, Parallels Desktop.
Client testing environments and engineering laptops.
Virtual Switching (vSwitches)
When you build a VM, it doesn't plug into a physical switch port. It plugs into a logical, software-defined vSwitch created by the hypervisor. This vSwitch is responsible for forwarding traffic out of the server's physical Network Interface Cards (pNICs).
The Virtual Switch (vSwitch)
A software-based Layer 2 switch created by the hypervisor. It allows Virtual Machines to communicate with each other internally, and acts as the bridge connecting VMs to the physical network interface cards (pNICs) of the host server.
Bridged Mode
The VM connects directly to the physical network through the vSwitch. It pulls its own IP address from the physical DHCP server and appears as a completely independent machine on the LAN.
NAT Mode
The hypervisor acts as a mini-router. The VMs get internal, isolated IP addresses, and the hypervisor translates their traffic to share the Host machine's physical IP address when accessing the outside world.
Virtual Machines vs. Containers
While hypervisors virtualize physical hardware to run multiple Operating Systems, Container Engines (like Docker) virtualize the Operating System to run isolated applications without the massive overhead of a guest OS.
| Comparison | Virtual Machine (VM) | Container (Docker) |
|---|---|---|
| Architecture | Hardware-Level Virtualization. Each VM includes a full Guest Operating System (Windows Server, Ubuntu) running on top of virtualized hardware. | OS-Level Virtualization. Containers share the Host OS kernel. They only contain the application and its direct dependencies. |
| Overhead & Size | Heavy. A Windows Server VM might consume 40GB of disk space and 4GB of RAM just to sit idle. | Extremely Lightweight. A Docker container running a web server might only consume 50MB of disk space and a few megabytes of RAM. |
| Boot Time | Minutes (Requires a full OS boot sequence). | Milliseconds (Starts instantly as an isolated process). |
In a traditional MSP environment, you will mostly deal with Virtual Machines on ESXi or Hyper-V (e.g., spinning up a new Domain Controller). However, as clients migrate to modern architectures, you will increasingly troubleshoot cloud-native applications deployed as Docker containers running on Kubernetes.