2. Client-Side Virtualization¶
Everything in Lesson 1 was server-side virtualization — pve1 and pve2 running guests other people connect to remotely. Client-side virtualization is the same idea, but on an individual's own computer: software like VirtualBox, VMware Workstation, or Hyper-V, running a VM right there on someone's laptop.
Why someone would do this¶
- Testing software on an OS they don't want to install for real
- Running an old, unsupported OS just to use one piece of legacy software
- Running Linux tools from inside Windows (or the reverse)
- Safely opening something sketchy without risking the real machine
Snapshots¶
A snapshot freezes a VM's exact state so you can return to it later — you've seen this constantly in this course: every time the wiki gets updated, a snapshot of CT 251 is taken first, specifically so a bad change can be rolled back instantly instead of rebuilt from scratch.
Try it
Explain, in your own words, why taking a snapshot before making a risky change is standard practice — using the course wiki's own deploy process as your example.
Tip
A snapshot isn't a full independent backup — it's usually stored as a difference from a base disk. Lose or corrupt that base disk, and the snapshot built on top of it is gone too.
Play it
Open the Virtualization and Cloud Lab and use the Client-side & snapshots tab.