Lesson 43 of 60 beginner

Virtualization 101

One host, many systems

Open interactive version (quiz + challenge)

Real-world analogy

A hypervisor is an apartment building. Instead of one house per plot of land (one OS per physical server), you build a tall building that runs many apartments (VMs) on the same plot. Tenants don’t see each other; the building handles shared plumbing.

What is it?

Virtualization is the foundation of modern infrastructure. Even pure-cloud shops run virtualization under the hood. Know VMs, snapshots, templates, vSwitches, HA/vMotion — even at a conceptual level — and you can read any datacenter topology.

Real-world relevance

A 200-branch bank replaces 200 physical servers with a consolidated virtualization cluster at HQ and two DR sites. Power, cooling, hardware cost drops; deployments become minutes; DR becomes achievable. All thanks to hypervisors and templates.

Key points

Hypervisor types — Type 1 runs directly on hardware (VMware ESXi, Hyper-V Server, Proxmox KVM). Type 2 runs on top of an OS (VMware Workstation, VirtualBox). Production uses Type 1; learners use Type 2.
VMs vs containers — a quick note — VMs virtualize hardware (each has its own OS). Containers share the host kernel (lightweight, fast start). Both are useful; enterprises run both. You’ll meet Docker/Kubernetes conceptually throughout your career.
Key VM concepts — vCPU, vRAM, virtual disks (thin vs thick), virtual NIC, snapshot, template, clone, export/import. Enterprises build golden templates and clone.
Snapshots are not backups — A snapshot captures a moment in time for a VM, but long-lived snapshots bloat disk and break performance. Use for short-term rollback (hours, not weeks). Real backup goes to a separate system with offsite copies.
High availability and vMotion / Live Migration — Enterprise clusters can move a running VM between hosts with no downtime. HA restarts a VM on another host if a host fails. Magic at scale; mandatory for critical infra.
Resource overcommit — You can allocate more vCPU/vRAM than physical. Great for density; dangerous when all VMs spike at once. Monitor ‘ready time’ and memory ballooning if performance degrades.
Virtual networking in VMs — Virtual switches and port groups map VM NICs to VLANs and physical uplinks. Security policies (promiscuous, MAC changes, forged transmits) prevent common VM escapes.
When to use Proxmox or Hyper-V for home labs — Proxmox (free, Debian + KVM + LXC) is excellent for home labs. Hyper-V comes with Windows Pro/Server. VMware Workstation Player is free for non-commercial use. All teach real skills.

Code example

// VM home-lab starter plan

Host OS: Windows 11 Pro (Hyper-V) or Ubuntu (KVM) or Proxmox bare metal.

VMs to build, in order:
  1) Windows Server 2022 as DC01 (AD DS, DNS, DHCP)
  2) Windows 11 client joined to the domain
  3) Ubuntu 22.04 as web + ssh lab (for Linux drills)
  4) pfSense or OPNsense firewall (VLANs, routing, NAT)
  5) Optional: a second DC for replication testing

Habits:
  - Snapshot BEFORE risky config changes
  - Keep snapshots short-lived (delete after verifying)
  - Export working VMs as templates for quick rebuilds
  - Document VM specs and their purpose in a lab journal

Line-by-line walkthrough

1. Home-lab plan heading
2. Host OS options
3. Blank separator
4. VM list heading
5. DC VM
6. Client VM
7. Linux lab VM
8. Firewall VM
9. Optional second DC
10. Blank separator
11. Habits header
12. Snapshot before risky changes
13. Keep snapshots short-lived
14. Export working templates
15. Maintain a lab journal

Spot the bug

Junior uses VM snapshots as the ONLY backup for a production domain controller for 90 days.

Need a hint?

Why is this dangerous?

Show answer

Snapshots bloat, degrade performance, and break if the host dies. They are not a backup strategy. Deploy real backup: Veeam/Azure Backup/Rubrik with verified restores, offsite copies, immutable storage, and tested restore drills. Snapshots are fine for short windows (minutes/hours), not 90 days.

Explain like I'm 5

One big computer can pretend to be many small ones. Each little computer (VM) thinks it’s alone. That’s how one server runs the whole office instead of needing one per app.

Fun fact

VMware Workstation introduced many of the concepts you still use today — snapshots, teams, shared folders — in 1999. Two decades later, the same ideas power cloud datacenters serving billions of users.

Hands-on challenge

On your laptop, install VMware Workstation Player or Hyper-V. Build a Windows Server VM + a Windows 11 client VM. Snapshot the client before joining the domain, verify you can revert, then delete the snapshot.

More resources

Proxmox VE docs (Proxmox)
Hyper-V on Windows (Microsoft Learn)
Home lab tour (pick your platform) (Lawrence Systems)

Open interactive version (quiz + challenge) ← Back to course: IT Jobs Bootcamp