Getting Started with Proxmox VE on Common Hardware
A practical guide to installing and configuring Proxmox VE on used enterprise or consumer hardware for your homelab.
Proxmox Virtual Environment (VE) is one of the best platforms for running a homelab or small production environment. It combines KVM virtualization and LXC containers under a single management interface — all on top of Debian.
This guide walks through a real-world Proxmox deployment on retired enterprise hardware.
Hardware Requirements
You don’t need the latest hardware. Proxmox runs well on:
- CPU: Any x86-64 CPU with VT-x/AMD-V support. The more cores, the better.
- RAM: 8GB minimum, 32GB+ recommended for multiple VMs.
- Storage: An SSD for the OS and VM images is strongly recommended.
- Networking: At least one Gigabit Ethernet port.
I’ve personally deployed Proxmox on the following hardware:
| Hardware | Specs | Performance |
|---|---|---|
| Dell Optiplex 7050 SFF | i5-7500, 32GB DDR4, 512GB NVMe | Excellent for 8-10 light VMs |
| HP EliteDesk 800 G4 | i7-8700, 64GB DDR4, 1TB NVMe | Handles 15+ VMs easily |
| Custom build | Ryzen 5 5600G, 64GB DDR4 | Great balance of power and efficiency |
Installation
- Download the latest Proxmox VE ISO from proxmox.com
- Write it to a USB drive using
ddor Rufus - Boot from USB and follow the installer
# Example: write ISO to USB on Linux
sudo dd if=proxmox-ve_*.iso of=/dev/sdX bs=4M status=progress
# Verify after writing
sync
Post-Installation Configuration
After first boot, configure the basics:
# Update the system
apt update && apt dist-upgrade -y
# Disable the enterprise repository if you don't have a subscription
sed -i 's/^deb/#deb/' /etc/apt/sources.list.d/pve-enterprise.list
# Add the no-subscription repository
echo "deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription" \
> /etc/apt/sources.list.d/pve-no-subscription.list
# Enable IOMMU for PCI passthrough (if needed)
sed -i 's/^GRUB_CMDLINE_LINUX_DEFAULT="quiet"/GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"/' \
/etc/default/grub
update-grub
Storage Layout Best Practices
A practical storage layout for a single-node Proxmox server:
/dev/nvme0n1 (system disk)
├── local (Directory) → /var/lib/vz
│ ├── ISO images
│ └── Container templates
├── local-lvm (LVM-Thin) → VM disks and CT rootfs
│ └── Thin-provisioned storage pool
└── Optional: Separate SSD/dataset for backups
First VM Deployment
Create your first VM using an Ubuntu cloud image:
# Download the cloud image
wget https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img \
-O /var/lib/vz/template/iso/
# Create VM from CLI
qm create 100 \
--name ubuntu-base \
--memory 2048 \
--cores 2 \
--net0 virtio,bridge=vmbr0 \
--scsihw virtio-scsi-pci
Security Considerations
- Change the default root password immediately
- Restrict SSH access to key-based authentication only
- Use the Proxmox firewall — it’s iptables-based and integrated
- Create non-root users for daily administration
- Keep the system updated — set up unattended-upgrades for security patches
Next Steps
Once Proxmox is running, consider:
- Setting up Proxmox Backup Server (PBS) for automated VM backups
- Creating LXC containers for lightweight services
- Setting up a Docker host VM for container workloads
- Configuring VLAN-aware networking for segmentation
Proxmox is one of the most capable platforms for homelab and small-scale production. The learning curve is manageable, and the results are professional-grade infrastructure.