Why Virtualize?
Consolidation, snapshots, dev/staging, HA intro.
Learning objectives
- Explain the business and technical reasons to virtualize servers
- Identify workloads that benefit from VMs vs those that should stay bare metal
- Estimate resource savings for a small-business consolidation scenario
The problem: one app, one box
For decades, the default pattern was one physical server per application. Database on one box, web on another, files on a third. Each OS needed patching, monitoring, backups, and spare hardware. Most servers sat idle overnight — Workshop Co.'s booking system gets heavy traffic Saturday mornings and almost none on Tuesday afternoons.
Virtualization lets you run many isolated guest operating systems on one physical host. Each guest thinks it has its own CPU, RAM, disk, and network. The hypervisor maps those virtual resources to real hardware.
Why organizations virtualize
| Benefit | What it means for Workshop Co. |
|---|---|
| Consolidation | Three physical servers → one Proxmox host with three VMs |
| Isolation | Database crash does not take down the website VM |
| Fast provisioning | Clone a staging VM in minutes, not weeks to buy hardware |
| Snapshot & backup | Point-in-time recovery before a risky PostgreSQL upgrade |
| Portability | Move VMs to new hardware without reinstalling OSes |
Small businesses from Edmonton to Halifax often keep servers in closets or basements. Virtualization reduces power bills (important in provinces with higher electricity rates) and lets a part-time IT person manage one host instead of a shelf of aging Dell towers.
Worked example — Workshop Co. consolidation
Current state:
- web-01 — 4 cores, 8 GB RAM, 256 GB SSD (avg 15% CPU)
- db-01 — 4 cores, 16 GB RAM, 512 GB SSD (avg 25% CPU)
- files-01 — 2 cores, 8 GB RAM, 2 TB HDD (avg 5% CPU)
Proposed Proxmox host: 8-core CPU, 64 GB RAM, 2 TB NVMe + 4 TB HDD pool.
Install Proxmox VE on host
Create VM: web (2 vCPU, 4 GB)
Create VM: db (4 vCPU, 12 GB)
Create VM: nextcloud (2 vCPU, 4 GB)
Reserve ~16 GB for host + overhead
Total allocated: 8 vCPU, 20 GB RAM — well within the 64 GB host with room for growth and a staging VM.
High-performance GPU rendering, ultra-low-latency trading, or workloads needing dedicated NVMe throughput may stay on bare metal. Workshop Co.'s woodworking class booking app is a perfect virtualization candidate.
Try it yourself
Workshop Co. wants to add a staging.workshopco.ca environment identical to production. On three physical servers, what would that cost in hardware and time? On one Proxmox host?
Sample answers
- Physical: Duplicate three machines or accept shared staging — weeks of procurement, thousands of dollars
- Virtual: Clone three VMs from templates — under an hour, no new hardware
Check your understanding
- Does virtualization reduce the total RAM Workshop Co. needs across all workloads?
- Name one risk of putting all VMs on one physical host.
Answers
- Not necessarily — you still need enough RAM for all guests plus the host. You reduce wasted RAM on underutilized boxes and eliminate duplicate hardware.
- Single point of failure — if the host dies, all VMs go down unless you have clustering or good backups.