Introduction
A lot of people buy a mini PC for a totally different reason — a cheap desktop, a media box, an office machine — and only later realize it's basically a tiny, silent, low-power server. An Intel NUC, a Beelink, a Minisforum box, an old HP EliteDesk or ProDesk off eBay — these things usually have four or more CPU cores, support for 32-64GB of RAM, an NVMe slot, and they idle at 8-15 watts. That's a genuinely good Proxmox VE host, and it costs a fraction of a rack server in both money and electricity.
The catch is that mini PCs weren't designed with virtualization hosting in mind, so a few things behave differently than they would on a tower desktop or a Dell/HPE rack server. BIOS menus hide the settings you need in odd places, most models only have one network port, and there's no iDRAC or iLO to fall back on if something goes wrong during setup. None of that is a dealbreaker. You just need to know where to look before you start.
This guide walks through a full install of Proxmox VE 9.2 on mini PC hardware, from checking whether your specific box can even run it, through the BIOS settings that trip people up, to the first boot and initial cleanup once you're in.
What You Will Learn
- How to check whether your mini PC can actually run Proxmox VE before you waste an evening on it
- Where to find the virtualization and boot settings in a typical mini PC BIOS
- How to build a bootable Proxmox VE installer and get through setup on small-form-factor hardware
- What to do about the single network port most mini PCs ship with
- The specific errors mini PC owners run into, and how to fix each one
What Is This Feature?
Proxmox VE is a free, open-source virtualization platform built on Debian Linux. You install it directly onto the hardware — there's no host operating system underneath it — and from there it lets you run multiple virtual machines (VMs) and Linux containers (LXC) on that one physical box, each isolated from the others.
A "mini PC" in this context means any small-form-factor x86 machine: an actual Intel NUC, or one of the many similar boxes from Beelink, Minisforum, GMKtec, ASUS (the PN and ExpertCenter lines), or a refurbished corporate desktop like an HP EliteDesk 800 Mini or Dell OptiPlex Micro. They share the same basic shape: one CPU socket (soldered, usually), two SO-DIMM slots, one or two M.2 NVMe slots, and typically a single 1GbE or 2.5GbE Ethernet port.
None of that is unusual hardware from Proxmox VE's point of view — it's still just an x86-64 Linux install. The differences that matter are all in the BIOS and in how many network ports you have to work with, and that's what this guide focuses on.
Why Would You Use It?
The honest answer: price and power draw. A used enterprise server with real RAID and IPMI is more capable, but it's also loud, it pulls 80-150 watts sitting idle, and a lot of homelab users don't have anywhere to put something that sounds like a hair dryer. A mini PC sits on a shelf, makes almost no noise, and costs a few dollars a month in electricity even running 24/7.
For a first Proxmox VE box, a mini PC is honestly a better starting point than a full server. You'll run a handful of LXC containers (Pi-hole, a media server, maybe Home Assistant) and one or two VMs, and 16-32GB of RAM covers that comfortably. If you outgrow it later, everything you learn — storage, networking, backups — carries straight over to bigger hardware.
Where a mini PC falls short: heavy GPU passthrough setups, anything needing more than two NVMe drives, and workloads that actually need ECC memory. If that's what you're planning, look at a proper tower or rack build instead.
Prerequisites
Before you start, make sure you have:
- A mini PC with a 64-bit CPU (basically anything from the last decade), at least 8GB of RAM (16GB is a much more comfortable minimum), and 128GB+ of storage — NVMe strongly preferred over eMMC
- A USB flash drive, 8GB or larger, that you don't mind wiping
- A monitor and keyboard for the initial install (you only need these once — everything after that is done from the web interface)
- An Ethernet cable. Wi-Fi is not a supported option for the main Proxmox VE network, and trying to make it work is more trouble than it's worth
- The current Proxmox VE ISO, downloaded from proxmox.com/downloads
- A router or switch port with DHCP available, so the installer can pull an IP address automatically
One thing worth checking ahead of time: does your CPU support VT-x (Intel) or AMD-V? Almost every CPU sold since roughly 2012 does, but it's sometimes disabled in the BIOS by default on consumer boards. We'll turn it on in the tutorial below either way.
Step-by-Step Tutorial
Step 1: Confirm your hardware can run it
Boot the mini PC into whatever OS it currently has (or a Linux live USB if it's blank) and check for virtualization support:
egrep -c '(vmx|svm)' /proc/cpuinfoAny number greater than 0 means your CPU supports hardware virtualization. If you get 0, virtualization is either disabled in the BIOS (most likely) or genuinely unsupported (rare on anything made after 2012).
Step 2: Build the installer USB
Download the Proxmox VE ISO, then write it to your USB drive. On Windows, use Rufus in DD mode. On macOS or Linux, use balenaEtcher, or the command line:
sudo dd if=proxmox-ve_9.2-1.iso of=/dev/sdX bs=1M status=progress conv=fsyncReplace /dev/sdX with your actual USB device — check with lsblk first, and double-check it. This command overwrites the entire target device with no confirmation prompt.
Step 3: Get into the BIOS and set it up correctly
Power on the mini PC and hit the BIOS key repeatedly during boot. It varies by brand: F2 or Del on most Intel NUCs and Minisforum boxes, F7 on some Beelink units, F10 on HP EliteDesk/ProDesk minis. Once you're in, look for these three settings — the exact menu names vary, but they're almost always there:
- Intel Virtualization Technology (VT-x) or SVM Mode on AMD — set to Enabled. Usually under Advanced > CPU Configuration.
- VT-d (Intel) or IOMMU (AMD) — enable this too, even if you're not planning to pass through a GPU or NIC right away. It's much easier to turn on now than to remember it later.
- Secure Boot — set to Disabled. The Proxmox VE installer works with Secure Boot on newer releases, but it causes enough headaches with third-party kernel modules down the line that disabling it up front saves you trouble.
While you're in there, set the boot mode to UEFI (not Legacy/CSM) and move the USB drive to the top of the boot order. Save and exit — usually F10.
Step 4: Run the installer
The machine should boot straight into the Proxmox VE installer menu. Pick the graphical install option. The wizard is straightforward:
- Accept the license and select your target disk. On a mini PC this is almost always your single NVMe drive.
- Set your country, time zone, and keyboard layout — this also determines your default mirror for updates.
- Set the root password and an admin email address (used for system notifications later).
- Configure the network: pick your Ethernet interface, set a hostname (like
pve.home.lan), and either take the DHCP-assigned IP or set a static one now. A static IP is worth doing here if you already know what you want — it saves a step later.
Review the summary screen and confirm. The install itself takes about 5-8 minutes on NVMe storage. The machine reboots automatically when it's done — pull the USB drive during that reboot.
Step 5: Log in to the web interface
Once it's back up, you don't need the monitor and keyboard anymore. From any other computer on the same network, open a browser and go to:
https://<your-mini-pc-ip>:8006You'll get a certificate warning — that's expected, Proxmox VE uses a self-signed certificate out of the box. Click through it (Advanced > Proceed in Chrome, Accept the Risk in Firefox) and log in with username root and the password you set during install.
Step 6: Update the system and fix the repository warning
New installs show a yellow "No valid subscription" banner the first time you log in. That's normal — it just means you're pointed at the enterprise repository, which requires a paid subscription. Switch to the free no-subscription repo instead. Open the Shell (Node > Shell in the web UI, or SSH in) and run:
echo "deb http://download.proxmox.com/debian/pve trixie pve-no-subscription" > /etc/apt/sources.list.d/pve-no-subscription.list
rm /etc/apt/sources.list.d/pve-enterprise.list
apt update && apt full-upgrade -yReboot once the upgrade finishes if it pulled in a new kernel — the web UI will tell you if a reboot is pending under Node > Summary.
Commands Explained
| Command | What it does |
|---|---|
egrep -c '(vmx|svm)' /proc/cpuinfo | Counts CPU cores reporting virtualization extensions. Zero means it's off in the BIOS or not supported. |
lsblk | Lists block devices (drives and partitions) so you can identify the right USB device before writing the ISO to it. |
dd if=... of=/dev/sdX bs=1M | Copies the ISO byte-for-byte onto the USB drive, making it bootable. There's no undo — it silently erases whatever was on that drive. |
apt update | Refreshes the local list of available packages and their versions from the configured repositories. Doesn't install anything by itself. |
apt full-upgrade -y | Installs available updates, including ones that require removing or replacing packages (used instead of plain upgrade for kernel updates). |
pveversion | Prints the installed Proxmox VE version and build, useful when asking for help or checking you're current. |
Common Errors
"No bootable device found" on boot. The USB drive isn't first in the boot order, or the ISO wasn't written correctly. Recheck the boot order in BIOS, and if that's fine, rewrite the USB drive — a corrupted download or a flaky flash drive is the usual cause.
Installer boots but the screen goes black right after the Proxmox logo. This is a known quirk on some mini PCs with newer Intel iGPUs where the default framebuffer driver misbehaves. At the boot menu, edit the install option and add nomodeset to the kernel boot line, then try again.
Can't reach the web interface after install. Nine times out of ten this is either a typo in the IP address, or you're trying http:// instead of https:// on port 8006. Double check both. If it still fails, confirm the machine actually got an IP by reconnecting the monitor and running ip a.
"This kernel requires the following features not present on the CPU: pse" or similar CPU feature errors on very old mini PCs. Proxmox VE 9.x has minimum CPU requirements that exclude some early Atom-based mini PCs from around 2013-2015. If you hit this, you need older hardware or an older Proxmox VE major version — there's no BIOS fix for a missing instruction set.
Troubleshooting
If virtualization support showed as 0 in Step 1 even after enabling VT-x/AMD-V, double check you saved the BIOS settings before rebooting — some BIOS menus need you to explicitly select "Save and Exit" rather than just closing out. It's an easy step to miss.
If the install completes but VMs refuse to start afterward with a KVM-related error, run egrep -c '(vmx|svm)' /proc/cpuinfo again from the Proxmox VE shell itself. If it still comes back 0, the setting didn't actually take in the BIOS, or you're on a CPU that doesn't support it at all — check your exact CPU model against Intel's or AMD's spec page.
If you only have one Ethernet port and you were hoping to give VMs their own separate network, you can't do that with a single physical NIC without a managed switch and VLANs. The default single-bridge setup (vmbr0) shares your one port between the host and every VM/container, and for a homelab that's genuinely fine — you don't need multiple physical NICs to get value out of Proxmox VE.
If updates fail with a GPG or repository error, it usually means the pve-enterprise.list file wasn't actually removed in Step 6. Check /etc/apt/sources.list.d/ for leftover files pointing at the enterprise repo and delete them, then run apt update again.
Best Practices
Use the wired Ethernet port, not a USB Wi-Fi dongle, even if that means running a longer cable across the room. Wi-Fi adapters aren't reliably supported for the host network, and even when they technically work, you'll fight dropped connections at the worst possible time.
Go into the BIOS and set "Restore on AC Power Loss" (sometimes called "After Power Failure") to Power On. Mini PCs get unplugged, moved, or lose power during an outage more often than rack servers do, and you don't want to drive home to press a button.
Spend the extra $15-20 on an NVMe drive instead of relying on built-in eMMC storage if your model has both options. eMMC is slow enough that VM disk I/O becomes the actual bottleneck, not your CPU or RAM.
Set up email notifications (Datacenter > Notifications) before you actually need them. A dead fan or a failed backup job is much less painful to catch the day it happens than a week later.
Take a backup before your first real configuration change, even something as small as editing the network bridge. It costs five minutes and it's the difference between an annoying afternoon and a full reinstall if something goes sideways.
Frequently Asked Questions
Can I use any mini PC for Proxmox VE?
Almost any x86-64 mini PC from the last decade works, as long as it supports VT-x/AMD-V and meets the minimum CPU feature set for your Proxmox VE version. ARM-based mini PCs are a separate case and not covered here.
Do I need a dedicated GPU?
No. Proxmox VE itself runs headless with no GPU requirement at all. You'd only need one if you're planning GPU passthrough into a VM for something like Plex hardware transcoding or a gaming VM.
Is 8GB of RAM enough?
It'll technically install and run, but you'll be limited to two or three lightweight LXC containers. 16GB is a realistic minimum for a useful homelab, and 32GB gives you real breathing room.
What about the single network port?
It's not a blocker. Proxmox VE creates one bridge (vmbr0) that all your VMs and containers share with the host by default, and that's how most homelab setups actually run, single NIC or not.
Will a mini PC be loud running 24/7?
Most modern mini PCs use laptop-class cooling and stay near-silent under normal homelab load. They'll spin up under sustained heavy CPU load, but idle noise is usually a non-issue.
Can I upgrade the RAM and storage later?
On most models, yes — SO-DIMM slots and M.2 slots are user-accessible behind a bottom panel. A few ultra-compact models solder the RAM, so check your specific model's specs before buying with future upgrades in mind.
Conclusion
None of this is complicated once you've done it once — the BIOS settings are the only real difference from installing on a tower or a server, and now you know exactly where to look for them. Get VT-x and VT-d turned on, disable Secure Boot, and the rest of the install is identical to any other x86 hardware.
From here, the next reasonable steps are creating your first VM or LXC container, setting a static IP if you didn't during install, and getting backups configured before you put anything important on it. A mini PC won't replace a rack of enterprise gear, but for a first Proxmox VE host, or a permanent low-power homelab box, it's hard to beat what it costs to run.