Proxmox VE — Home Lab Hypervisor

Proxmox Virtual Environment (Proxmox VE) is a free, open-source bare-metal hypervisor based on Debian Linux. It runs virtual machines (via KVM/QEMU) and Linux containers (LXC) from a single unified web interface. The management UI runs on port 8006 over HTTPS.

Installation

  1. Download the Proxmox VE ISO from proxmox.com/downloads
  2. Flash to USB with Balena Etcher or Rufus
  3. Boot from USB on your server hardware (old PC, mini PC, NUC, or dedicated server)
  4. The installer sets up Debian + Proxmox VE automatically
  5. Set a static IP, hostname, DNS, and root password during install
  6. After install: browse to https://[ip]:8006 — accept the self-signed certificate warning

Dismiss the Subscription Nag (Free Usage)

Proxmox shows a "No valid subscription" popup on every login for non-subscribers. To remove it for home use:

# SSH into Proxmox host, then:
sed -i.bak "s/data.status !== 'Active'/false/g" \
  /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
# Restart the web service
systemctl restart pveproxy
# The popup is gone until next Proxmox update (re-run after updates)

Switch to Free Community Repository

# Remove enterprise repo (requires subscription)
rm /etc/apt/sources.list.d/pve-enterprise.list

# Add free community repo
echo "deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription" \
  > /etc/apt/sources.list.d/pve-community.list

# Update
apt update && apt dist-upgrade

VM vs LXC Container

FeatureKVM VMLXC Container
OS supportAny (Windows, Linux, BSD)Linux only
RAM overheadHigh (full kernel)Low (shared kernel)
Boot time30–60 seconds1–3 seconds
IsolationComplete (separate kernel)Process-level
Storage efficiencyLowerHigher
Use caseWindows, untrusted workloads, full isolation neededLinux services: Pi-hole, HA, media servers

Create an LXC Container (Common for Home Lab Services)

  1. Datacenter → your node → Create CT (top right)
  2. Set hostname, password, and SSH key
  3. Template: click the download icon to get Ubuntu, Debian, Alpine, etc. from the Proxmox template library
  4. Storage: assign disk size (4–20 GB is typical for services)
  5. CPU: 1–2 cores for most services
  6. Memory: 512 MB–2 GB depending on the service
  7. Network: DHCP for easy setup, or static IP
  8. Confirm and Start after creation

Proxmox Storage

Storage TypeBest ForNotes
local-lvm (default)VM disks, LXC containersLVM thin-provisioned, efficient
dir (local)ISOs, backups, templatesFiles on filesystem, shareable
ZFSNAS, data integritySnapshots, RAID, checksumming
NFS/SMBShared storage from NASMount a NAS share as Proxmox storage
CephClustered, high-availabilityMulti-node clusters, distributed storage

Backup and Snapshot

Proxmox supports VM/container backups and snapshots from the web UI. Backups dump a complete VM/container archive to storage. Snapshots capture the current state and can be reverted instantly — useful before risky updates.

Schedule automated backups: Datacenter → Backup → Add schedule. Select which VMs/containers to include, destination storage, and time. Backups run in the background and can be sent to a NFS share or external storage.

Troubleshooting

Cannot reach :8006 after install: The server may still be booting. Check for IP assignment — run ip addr on the Proxmox console. If IP is correct, check: systemctl status pveproxy. Your browser may also block self-signed certificates — proceed through the security warning.

No internet in LXC container: DNS and gateway may not be set. In the container's network settings, verify the gateway IP and DNS are populated. Also check if the host's network bridge (vmbr0) is correctly configured — Datacenter → your node → Network.