How to Install Proxmox on a Mini PC — Step-by-Step Guide | Mini PC Lab
By Mini PC Lab Team · January 22, 2026 · Updated March 27, 2026
This article contains affiliate links. If you purchase through our links, we may earn a commission at no extra cost to you. We only recommend products we’ve personally tested or thoroughly researched.

Installing Proxmox VE on a mini PC takes about 20–30 minutes from download to first login. This guide covers the complete process: preparing the USB installer, configuring BIOS for virtualization, running the Proxmox installer, and completing the essential post-install configuration that the official docs skip.
Before You Start
Requirements:
- Mini PC with 8GB+ RAM (16GB recommended for running VMs)
- 64GB+ NVMe SSD (separate from any existing OS drive)
- USB drive, 8GB minimum, for the installer
- A second computer to create the bootable USB
- Network cable (recommended — Wi-Fi setup is more complex on Proxmox)
- Estimated time: 20–30 minutes
Recommended hardware if you’re still choosing: See our best mini PC for Proxmox guide for tested models. Short answer: Beelink SER9 PRO+ or Minisforum UM790 Pro for mid-range, Beelink EQ14 for budget.
Step 1: Download Proxmox VE
Go to proxmox.com/downloads and download the latest Proxmox VE ISO. As of March 2026, the current release is Proxmox VE 8.3.
Download the .iso file — it’s approximately 1.2GB.
Step 2: Create the Bootable USB
On Windows — use Rufus:
- Download Rufus from rufus.ie
- Insert your USB drive (8GB+)
- In Rufus: select the Proxmox ISO, leave partition scheme as MBR or GPT (Rufus detects correctly), write mode as “DD Image”
- Click Start → accept the warning → wait for completion (~5 minutes)
On macOS or Linux — use dd:
# Find your USB device (look for the disk matching your USB size)
diskutil list # macOS
lsblk # Linux
# Write the ISO (replace /dev/diskX with your USB device — do NOT use a partition like /dev/disk2s1)
sudo dd if=proxmox-ve_8.3-1.iso of=/dev/diskX bs=4M status=progress conv=fsync
The USB is ready when the command completes without errors.
Step 3: Configure BIOS for Virtualization
Boot your mini PC into BIOS (typically F2, F7, Delete, or the brand-specific key on startup — check your model’s documentation).
Required settings:
Virtualization Technology (VT-x): Enabled
VT-d (Intel) / AMD-Vi (AMD): Enabled
Secure Boot: Disabled
Fast Boot: Disabled
Boot from USB: Enabled
IOMMU (required for PCIe passthrough later):
- Intel: Enable
VT-din CPU or Advanced settings - AMD: Enable
AMD-ViorIOMMUin CPU settings — often listed as “SVM Mode”
On most mini PCs, VT-x is enabled by default. VT-d/AMD-Vi may need to be explicitly turned on. Secure Boot must be disabled for Proxmox to boot from USB.
Save and exit BIOS.
Step 4: Boot from USB and Run the Installer
- Insert the USB and power on the mini PC
- Enter the boot menu (usually F7, F11, or F12 during POST)
- Select your USB drive from the boot device list
- The Proxmox GRUB menu appears — select “Install Proxmox VE (Graphical)”
In the Proxmox installer:
Target hard disk: Select your NVMe SSD. If you have multiple disks, choose carefully. Proxmox will erase the selected disk completely.
File system options:
ext4— reliable, well-supported, good default choiceZFS (RAID0)— only if you have a single disk and want ZFS features (snapshots, compression). Requires 4GB+ RAM overhead.- For most mini PC setups with one NVMe: ext4 is the right choice
Country, timezone, keyboard: Set your locale.
Password and email: Set the root password (you’ll use this to log in to the web UI). Enter a valid email address — Proxmox sends alerts here.
Network configuration:
- Management interface: select your wired Ethernet port (e.g.,
enp2s0) - Hostname: something like
pve01.localorproxmox.home - IP address: Assign a static IP on your home network (e.g.,
192.168.1.50) - Gateway: your router’s IP (e.g.,
192.168.1.1) - DNS: your router’s IP or
1.1.1.1
Confirm and install. Installation takes 5–10 minutes. The system reboots automatically.
Step 5: First Login
Remove the USB drive after reboot. Proxmox boots to a text console showing:
Proxmox Virtual Environment 8.3
https://192.168.1.50:8006/
Open a browser on another machine and navigate to https://[YOUR-IP]:8006. Accept the self-signed certificate warning. Log in with:
- Username:
root - Realm:
Linux PAM standard authentication - Password: the password you set during installation
The Proxmox web UI loads.
Step 6: Post-Install Configuration (Do This Before Anything Else)
6a. Disable the “No Valid Subscription” Nag
Proxmox shows a subscription warning on every login if you’re using the free community edition. Dismiss it or remove it:
# SSH into your Proxmox node (or use the Shell in the web UI)
sed -i.bak "s/data.status !== 'Active'/false/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
systemctl restart pveproxy
6b. Switch to the Community Repository (No Subscription Required)
The default Proxmox repository requires a paid subscription. For home use, use the free community repo:
# Disable the enterprise repository
echo "# deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise" > /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
# Also fix the Ceph enterprise repo if present
echo "# deb https://enterprise.proxmox.com/debian/ceph-quincy bookworm enterprise" > /etc/apt/sources.list.d/ceph.list
# Update
apt update && apt full-upgrade -y
6c. Enable IOMMU in the Kernel (Required for GPU/PCIe Passthrough)
Edit the GRUB bootloader config to pass the IOMMU parameter:
# For Intel systems
sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="quiet"/GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"/' /etc/default/grub
# For AMD systems
sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="quiet"/GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt"/' /etc/default/grub
# Apply changes
update-grub
reboot
After reboot, verify IOMMU is active:
dmesg | grep -e DMAR -e IOMMU
# Should show: DMAR: IOMMU enabled (Intel) or AMD-Vi: IOMMU enabled (AMD)
6d. Configure Email Alerts (Optional but Recommended)
Proxmox can email you when VMs crash or disks degrade. Configure with a Gmail app password or a relay:
apt install -y libsasl2-modules mailutils
# Configure relay (example using Gmail SMTP)
cat > /etc/postfix/sasl_passwd << EOF
smtp.gmail.com [email protected]:app-password
EOF
postmap /etc/postfix/sasl_passwd
# Test
echo "Proxmox test" | mail -s "Test" [email protected]
Step 7: Create Your First VM
- In the Proxmox web UI, click Create VM (top right)
- General: Name your VM (e.g.,
debian-12) - OS: Upload an ISO first via Datacenter → Storage → local → ISO Images → Upload. Then select it.
- System: Keep defaults (SeaBIOS, VirtIO SCSI)
- Disks: 32GB+ for a Linux VM, 60GB+ for Windows
- CPU: 2 cores minimum, 4 recommended for desktop VMs
- Memory: 2048MB minimum, 4096MB for comfortable use
- Network: Default bridge
vmbr0— connects the VM to your local network - Confirm: Review and click Finish
Start the VM from the web UI and access it via the Console tab (VNC).
Create Your First LXC Container (Lighter Than a VM)
For running services like Pi-hole, Nginx, or Vaultwarden, LXC containers use far less RAM and CPU than full VMs:
- Download a template: Datacenter → Storage → local → CT Templates → Templates → search “debian-12” → Download
- Click Create CT in the top right
- General: Name it, set a root password
- Template: Select the Debian 12 template
- Disks: 8GB is sufficient for most services
- CPU: 1 core
- Memory: 512MB for light services; 1024MB for services with web UIs
- Network: DHCP on
vmbr0
Start the container and click Console to access the shell.
Troubleshooting
Proxmox fails to boot after install
Check that Secure Boot is disabled in BIOS. On some mini PCs, Secure Boot re-enables after the BIOS update — go back in and disable it again.
No network in the Proxmox web UI
If your mini PC uses a Realtek NIC, the driver may need additional configuration. Check:
ip link show
# Should show your NIC (enp2s0 or similar) with UP status
If the interface is down:
ip link set enp2s0 up
dhclient enp2s0
For persistent issues with Realtek NICs, adding r8169 to /etc/modules and rebooting often resolves it.
”No IOMMU” warning when creating VMs
Verify IOMMU is enabled in both BIOS (Step 3) and kernel (Step 6c). Some mini PCs have IOMMU disabled by default and the BIOS option may be labeled differently — look for “VT-d,” “AMD-Vi,” “IOMMU,” or “SVM Mode.”
Proxmox web UI is slow
First, disable the no-subscription popup as described in Step 6a. If the UI is still slow, it may be a certificate issue — try clearing your browser cache or using a different browser.
What to Do Next
With Proxmox installed and configured, the common next steps are:
- Install a Debian VM as a general-purpose server for Docker containers
- Set up TrueNAS SCALE in a VM for NAS storage — see our best mini PC for TrueNAS guide
- Run OPNsense as a VM with NIC passthrough — see our best mini PC for OPNsense guide
- Configure GPU passthrough if you have a Radeon 780M or discrete GPU — see our Proxmox GPU passthrough guide
For hardware selection, our best mini PC for Proxmox guide covers the top tested options across all budgets.
Quick Price Summary
- Beelink EQ14 — budget Proxmox host
- Beelink SER9 PRO+ — mid-range, 8-core Ryzen 7
- Minisforum UM790 Pro — proven Proxmox platform
Recommended Hardware
→ Check Current Price: Beelink EQ14 on Amazon — budget Proxmox host, Intel N150, dual Intel 2.5GbE → Check Current Price: Beelink SER9 PRO+ on Amazon — mid-range, 8-core Ryzen 7, 8W idle → Check Current Price: Minisforum UM790 Pro on Amazon — proven Proxmox platform, 64GB DDR5 support