4 Ways Proxmox Turned My Old PC Into the Ultimate Home Server
Proxmox VE transforms old hardware into a powerful homelab workhorse. Here's how to leverage its enterprise-grade features for your home setup.
Proxmox Virtual Environment is the open-source hypervisor that serious homelab enthusiasts swear by. It combines KVM virtualization with LXC containers, a web-based management interface, and enterprise features like clustering and high availability—all without licensing fees. Here's how to turn that old desktop collecting dust into the ultimate home server.
1. Virtual Machines for Isolation
Proxmox lets you run multiple operating systems simultaneously on a single machine. Spin up a Windows VM for that one application that only runs on Windows, a separate VM for your pfSense router, another for macOS (for iOS development), and keep your home automation stack isolated on its own VM.
The performance overhead is minimal—KVM (Kernel-based Virtual Machine) runs VMs with near-native speed using hardware virtualization extensions (VT-x/AMD-V). An old i5-6600K with 32GB RAM can comfortably run 5-8 VMs simultaneously for home use cases.
Key advantage: when one VM misbehaves or gets compromised, it doesn't take down your other services. Complete isolation at the hypervisor level means you can test risky configurations, run untrusted software, or experiment with new OSes without risking your core home server.
2. LXC Containers for Lightweight Services
LXC (Linux Containers) provides the speed and density of containers like Docker, but with full systemd initialization and traditional init scripts. Unlike Docker, LXC containers boot like real machines with their own kernel, systemd, and services.
Run your Home Assistant OS as an LXC, your Plex server in another, your Pi-hole in a third. Proxmox's implementation supports nesting (running Docker inside LXC), GPU passthrough, and resource limits (CPU, RAM, disk I/O quotas).
The efficiency is impressive: you can run 20+ LXC containers on modest hardware where running 20 VMs would be impossible. Each container starts in seconds, uses minimal overhead, and can be snapshotted, cloned, or migrated to other Proxmox nodes with a few clicks.
3. ZFS Storage for Data Protection
Proxmox includes native ZFS support, the same filesystem used in NAS appliances costing thousands. ZFS provides:
- Copy-on-write snapshots: Take point-in-time snapshots automatically. Ransomware can't delete your backups if they're stored as immutable snapshots.
- Data integrity verification: Every block is checksummed. Silent data corruption is detected and repaired automatically (known as self-healing).
- Compression: LZ4 compression gives 2-4x storage density for typical workloads with negligible CPU overhead.
- Raid-Z redundancy: Software RAID that handles disk failures gracefully, rebuilds automatically, and doesn't require a hardware RAID controller.
Set up a Raid-Z2 pool (can survive 2 disk failures) with 4+ drives for your bulk storage. Even with consumer drives, ZFS's integrity features protect your data in ways that ext4/XFS never could.
4. GPU Passthrough for Media Transcoding
Proxmox supports PCI-e passthrough, allowing a VM to exclusively control a GPU. This unlocks hardware-accelerated transcoding for Plex, Jellyfin, or Emby without the licensing costs of CPU-only transcoding.
An old GTX 1060 or GTX 1070 in your Proxmox host can passthrough to a Plex VM and transcode 4K HDR streams while your CPU handles other tasks. Intel integrated graphics (iGPU) works even better—most modern CPUs support GVT-g for virtualizing the iGPU across multiple VMs.
For Home Assistant and similar AI workloads, GPU passthrough lets you run Ollama, local AI models, or TensorFlow workloads in a VM while keeping your host system clean and isolated.
Getting Started: Minimum Requirements
Proxmox runs well on hardware from 2015 onward. The sweet spot:
- CPU: Any Intel i5/i7 6th gen or newer, or AMD Ryzen (Zen+ or newer)
- RAM: 16GB minimum, 32GB recommended. ZFS loves RAM for caching.
- Storage: SSD for Proxmox OS and VM disks. Spinning disks for bulk ZFS storage.
- Network: Gigabit Ethernet minimum. 2.5GbE preferred for file transfers.
Installation Best Practices
Install Proxmox to a dedicated SSD (120GB sufficient) separate from your data storage. Use a USB 3.0 flash drive or SATA SSD for the OS—spinning disks are too slow for the hypervisor itself.
After installation, add the Proxmox No-Subscription repository for newer packages (not recommended for production, but fine for homelabs). Configure your network bridges during setup—Proxmox creates a vmbr0 bridge by default that your VMs use for networking.
Enable the Proxmox firewall at the cluster level for security. Even on a home network, this gives you fine-grained control over traffic between VMs and containers.
The Homelab Dashboard You'll Actually Use
Proxmox's web interface (port 8006) gives you a single pane of glass for your entire homelab. View resource usage across all VMs and containers, manage snapshots and backups, monitor ZFS pool health, access serial consoles, and configure networking—all without SSH'ing into the host.
Combined with cockpit or Portainer for container management within specific VMs, you get enterprise-grade infrastructure visibility at a fraction of the cost of commercial solutions.
The learning curve is real—Plan (think, KVM, ZFS, networking concepts)—but Proxmox has excellent documentation and an active community. The result is a home server that's more capable, more reliable, and more flexible than any consumer NAS or pre-built solution, running on hardware you already own.