Quick Summary (TL;DR): To install Proxmox Virtual Environment (VE) on a mini PCAliExpress price, check that the x86-64 CPU and BIOS support hardware virtualisation, back up anything on the target SSD, download the current Proxmox VE 9.2 x86-64 ISO from the official site and write it to a USB drive. Boot the mini PCAliExpress price from USB, choose an appropriate filesystem (usually ext4/LVM-thin for a straightforward single-SSD installation), and configure a fixed LAN IP, gateway, DNS and hostname. After reboot, open https://HOST-IP:8006, review updates and storage, upload a Debian installation ISO, then create a VM using a VirtIO network adapter attached to vmbr0 and a VirtIO SCSI disk. Install the guest OS, enable its QEMU guest agent and schedule backups to storage outside the mini PCAliExpress price. This is a bare-metal installation: the installer erases the selected target disk. This guide covers the initial host and first VM, not advanced GPU or Zigbee/Thread passthrough.
What You Are Installing—and When Proxmox Is Worth It
Proxmox VE is a Debian-based virtualisation host that runs full KVM/QEMU virtual machines and Linux containers (LXC). It replaces the operating system on the mini PCAliExpress price; it is not an app you install inside Windows. The host provides a browser-based console, virtual networking, storage management, snapshots and backup scheduling. A VM has its own kernel and operating system; an LXC container shares the Linux host kernel. The choice matters for isolation, operating-system support and maintenance.
A dedicated Home Assistant box generally does not need this extra layer. Proxmox earns its place when one machine must run several independently maintained workloads—perhaps Home Assistant OS, a Debian Docker VM, a monitoring VM and a temporary development environment. If you are still choosing the machine, see our mini PCs for Proxmox buying guide. If you only want Home Assistant, compare direct HAOS, Container and Proxmox before adding complexity.
This walkthrough uses the x86-64 Proxmox VE 9.2-1 installer listed by Proxmox on 10 October 2026. Proxmox also offers a separate Arm64 installer, but that is not the correct image for Intel N100AliExpress price/N150 or AMD Ryzen mini PCs. Interface labels and package versions can change after updates; follow the installer displayed on your own system if it differs slightly.
Before You Start: Hardware, Firmware and Network Checklist
| Item | Practical starting point | Check before installation |
|---|---|---|
| CPU / firmware | x86-64 Intel or AMD CPU with VT-x or AMD-V | Enable virtualisation in UEFI/BIOS; VT-d/AMD-Vi is separate and only needed for PCI(e) passthrough. |
| RAM | 8 GB for learning; 16 GB or more for multiple useful guests | Proxmox lists 2 GB for the host in recommended use, plus guest memory; do not treat 2 GB as a comfortable multi-VM total. |
| Internal storage | A reputable 256–512 GB SSD or larger | Back up existing data; check whether the M.2 slot is NVMe, SATA or both. |
| Networking | Wired Ethernet to the main LAN/switch | Know the router IP, subnet, DNS server and a genuinely unused management IP. |
| Installer media | USB flash drive with at least 4 GB usable capacity | USB writing will erase it; the current x86-64 ISO is listed at about 1.71 GB. |
| Console | Monitor, keyboard and power adapter | Have physical access for the first install and any network recovery. |
| Recovery | Separate backup disk/NAS and ideally a UPS | Do not put the only backup on the SSD being erased. |
The official Proxmox hardware requirements distinguish the absolute test minimum from production recommendations. An N100/N150-class mini PC can make a useful small lab, but RAM ceilings, SSD slots, cooling and Ethernet chipsets vary by exact model. Check the manufacturer’s BIOS documentation and memory limit rather than assuming that every machine with the same CPU accepts the same upgrades.
If you intend to pass a GPU, network card or storage controller directly to a VM later, confirm both CPU and motherboard support for IOMMU and inspect actual device groups after installation. Intel VT-x alone does not guarantee PCIe passthrough. For this first Debian VM, no device passthrough is required.
Decide on the SSD Layout Before Touching the Installer
The most expensive beginner mistake is not selecting a slower filesystem; it is accidentally erasing the wrong drive or creating a storage layout that leaves no room for VM disks. The installer offers choices such as ext4, XFS and ZFS, with different consequences. A single good SSD with ext4 and LVM-thin is usually the least complicated way to learn. ZFS can be excellent, especially with mirrored drives and sufficient memory, but it adds memory and administration considerations that a small one-SSD host may not need.
| Layout | Good fit | Advantages | Watch-outs |
|---|---|---|---|
| One SSD, ext4 + LVM-thin | First Proxmox host, light home lab | Straightforward install; commonly provides local and local-lvm storage | One SSD failure stops the host; backups must live elsewhere. |
| One SSD, ZFS | Users specifically learning ZFS | Checksumming, snapshots and ZFS tools | No redundancy from a single disk; higher memory use and added operational complexity. |
| Two SSDs, ZFS mirror | Always-on services needing drive-failure tolerance | A mirror can survive one disk failure if configured and maintained correctly | Usable capacity approximates one drive; still needs independent backups. |
| OS SSD + second VM SSD | Machines with two compatible slots | Separates host boot and VM I/O; easy capacity planning | Not automatically redundant; both disks can fail independently. |
| VM disks on NAS | Existing reliable fast network storage | Centralised storage and potentially simpler capacity expansion | Host depends on LAN/NAS; not ideal as the only storage for first setup. |
Understand the two common default storage names: with a typical ext4/LVM-thin installation, local is a directory storage used for ISOs, container templates and often backups, while local-lvm is a thin-provisioned pool used for VM and container disks. They are different logical allocations on the same physical SSD, not two independent disks. If you select ZFS or customise storage, the names and content types can differ; always inspect Datacenter → Storage rather than copying someone else’s layout.
A thin-provisioned 100 GB VM disk does not necessarily consume 100 GB immediately, but that does not make over-allocation free. If several guests write to a nearly full thin pool, they can all be affected. Keep free space, monitor pool utilisation and put backup archives on a separate target. Never rely on snapshots stored only on the same SSD as your disaster-recovery plan.
Download and Verify the Official Proxmox Installer
- Visit the official Proxmox VE ISO download page and select the x86-64 installer, not the Arm64 image.
- For the 9.2-1 ISO listed on 10 October 2026, Proxmox publishes SHA-256
4e88fe416df9b527624a175f24c9aa07c714d3332afb1ee3dbf3879573ef2c6c. Verify against the download page again if a newer ISO appears. - Write the ISO in image/raw mode to a disposable USB drive using a reputable imaging application. Do not copy the ISO as an ordinary file onto a formatted USB stick.
- Safely eject the USB drive, then connect it to the mini PC with the monitor, keyboard and Ethernet cable attached.
On Linux, calculate the checksum with the following command, changing the filename to match the file actually downloaded. On Windows, PowerShell’s Get-FileHash -Algorithm SHA256 provides the same check. A matching hash confirms the bytes match the published file; it does not make an untrusted download source trustworthy.
sha256sum proxmox-ve_9.2-1.iso
# Compare with the SHA256 shown on the official download pageThe installer is destructive. If this mini PC currently contains Windows, BitLocker recovery keys, photos or another operating system, export everything you need before proceeding. Disconnect external drives you do not intend to erase. A backup that has never been restored is not a proven recovery path.
Configure the Mini PC BIOS/UEFI
Power on the mini PC and enter firmware setup using the manufacturer’s key (commonly Del, F2 or Esc, but not universal). Menu names differ. Record the original settings before changing them, especially if the device is also used for other tasks.
- Enable Intel Virtualization Technology (VT-x) or AMD SVM/AMD-V. Without CPU virtualisation, KVM guests will not work as intended.
- Use a suitable UEFI boot mode. Choose the USB device from the firmware boot menu. Proxmox has supported Secure Boot in modern releases; do not disable it automatically unless the current installer or hardware requires it.
- Prefer wired Ethernet for management. A Linux bridge over Wi-Fi is not a drop-in replacement for an ordinary Ethernet bridge, and headless reliability is better with a cable.
- Consider Restore on AC Power Loss. For an always-on server, verify the BIOS can restart after a power failure; behaviour is model-specific.
- Leave advanced IOMMU and PCIe settings alone initially. Enable them only when needed and after confirming device isolation and firmware support.
For mini PCs with more than one Ethernet port, label the cable and note the port connected to the router/switch. The installer may offer several interfaces; picking an unplugged port for the management bridge can make the system look dead even when Proxmox has installed successfully.
Install Proxmox VE from USB
- Boot from the prepared USB drive. Choose the normal graphical installer if it works with your display. The terminal installer is an alternative on systems with awkward graphics output.
- Read the licence terms, then select the correct internal target SSD. Compare its model and capacity with what you checked beforehand. This disk will be overwritten.
- Open Options if you want to choose ext4/LVM-thin or a different supported filesystem. For a first single-SSD host, the default ext4 path is usually sensible. If using two drives for ZFS mirroring, confirm both selected drives are intended for erasure.
- Select country, timezone and keyboard layout. These affect logs and administration; guests can have their own timezone.
- Set a strong root password and a working email address for system notifications. Save the password in your password manager.
- Configure the management network deliberately: interface, fully qualified hostname, IP/prefix, gateway and DNS. Use the example below only after replacing it with values valid on your LAN.
- Review the summary carefully, start the installation, wait for completion, remove the USB drive and reboot.
Proxmox’s official getting-started instructions explicitly warn that the selected disks are erased. The install wizard does not preserve a Windows dual-boot configuration. If you need to retain an existing OS, stop and design a different installation approach instead of clicking through.
Choose the Correct Static IP, Gateway, DNS and Hostname
For a home server, a stable management address is more useful than a slightly faster CPU. Proxmox normally uses a static management IP; avoid selecting an address that your router may hand to another device. A DHCP reservation can help with planning, but the static address entered on the Proxmox host still needs to be unique and within the right subnet. Coordinate it with the router’s DHCP range.
| Setting | Illustrative value | Why it matters |
|---|---|---|
| Hostname / FQDN | pve1.home.arpa | A stable name; create local DNS/hosts resolution if your router does not supply it. |
| Management IP | 192.168.10.10/24 | A unique address on the management LAN; /24 means subnet mask 255.255.255.0. |
| Gateway | 192.168.10.1 | Usually your router; must be reachable on the host subnet. |
| DNS server | 192.168.10.1 | May be your router if it provides DNS forwarding; use your actual DNS service. |
| Physical NIC | The Ethernet interface with a live LAN cable | Becomes a port of the host’s Linux bridge. |
| Web interface | https://192.168.10.10:8006 | HTTPS on TCP port 8006; not plain HTTP. |
The example uses the reserved home-network domain home.arpa. If your router’s actual LAN is 192.168.1.0/24, copying 192.168.10.10/24 will isolate the host. Likewise, a hostname that cannot resolve locally may cause management confusion later. Record the exact IP and hostname before leaving the installer.
Avoid placing the management interface on an isolated VLAN until you have confirmed the switch port, router and firewall rules. A headless mini PC without out-of-band management is easy to lock out. Start with a simple untagged LAN connection; segment networks later after taking a configuration backup and arranging physical recovery access.
First Login: Web Interface, Certificate and Updates
From a second computer on the same LAN, visit https://192.168.10.10:8006 (substitute your actual host IP). The browser may warn about the initial self-signed TLS certificate. Verify that you are connecting to the IP you installed before accepting the local certificate warning; do not train yourself to ignore unexpected certificate errors on public sites.
Log in as root using the Linux PAM standard authentication realm (shown as root@pam in Proxmox). The interface is organised around Datacenter → node → storage/guests. If you see a subscription notice, that is not proof the installation failed: the software can run without a paid subscription, although the supported enterprise repository requires one.
- Confirm the node summary reports the expected CPU, RAM and installed Proxmox version.
- Open Datacenter → Storage. Identify where ISO images, backups and VM disk images are allowed. Do not assume that
local-lvmaccepts ISO uploads. - Open the node’s Repositories view and check the enabled package sources. For a non-subscribed home lab, follow Proxmox’s documented no-subscription repository option rather than leaving an inaccessible enterprise source as the only active PVE repository.
- Apply current updates through the node’s Updates panel and reboot if the kernel or other core components require it.
- Configure email notifications and, where practical, two-factor authentication for administrative accounts. Keep the management UI accessible only from trusted networks or a VPN.
Proxmox VE 9 uses Debian 13-era repository configuration, and newer installations may use deb822-style .sources files rather than the older .list examples found online. Do not paste a random Proxmox 7/8 repository snippet into a VE 9 installation. Use the current Proxmox repository guidance and the built-in UI, confirm the codename matches the installed release, and do not mix Debian and Proxmox major versions.
Useful read-only checks from Node → Shell are shown below. These confirm the software, addresses, default route and storage status without changing the host.
pveversion -v
ip -br address
ip route
pvesm status
lsblk -o NAME,SIZE,MODEL,TYPEHow Proxmox Networking Works: vmbr0 Is a Virtual Switch
The normal single-NIC installation creates a Linux bridge named vmbr0. Think of it as a software Ethernet switch: the physical NIC plugs into the bridge, the Proxmox management IP sits on the bridge, and each VM can attach a virtual NIC to that same bridge. The VM then appears on your LAN with its own MAC and IP address. This is not the same as a NAT-only network inside a desktop virtualisation app.
Router / LAN switch
| Ethernet
Physical NIC (for example eno1)
|
vmbr0 <-- Proxmox host management IP
/ \
/ \-- VM 101: Debian, separate LAN IP
\------ VM 102: future service VMInterface names vary: yours may be enp1s0, eno1 or another predictable Linux name. Do not paste an interface name from a tutorial. If the host has multiple NICs, the correct bridge port must match the cable you are using. A host IP placed directly on the physical NIC while that NIC is a bridge port can cause confusing connectivity failures.
| Symptom | Likely issue | First safe check |
|---|---|---|
| Proxmox UI works; VM has no LAN | VM NIC on wrong bridge, guest DHCP failure, or guest firewall | Inspect VM → Hardware → Network Device and guest IP settings. |
| No web UI after reboot | Wrong management IP, cable/NIC selection or route | Check console IP, cable link, ip -br address and ip route. |
| Can ping router, not public IP | Gateway/firewall or upstream routing | Verify gateway is in the host subnet; ping a known reachable public address. |
| Can ping public IP, not domains | DNS misconfiguration | Check resolver settings and local DNS reachability. |
| VM can reach LAN but not Internet | Gateway, DNS, VLAN or upstream policy for the guest | Check the guest’s IP/prefix, default route and DNS separately. |
Do not expose TCP 8006 to the public Internet by router port forwarding. Keep Proxmox administration on the LAN or behind a properly configured VPN, with strong credentials and updates. A reverse proxy by itself does not make an administrative hypervisor interface safe to expose.
Upload an ISO for Your First Virtual Machine
For a predictable first test, use a mainstream Linux guest rather than immediately importing a complex Home Assistant image or passing through devices. Debian’s official amd64 netinst image is a good choice: it is small, well documented and suitable for a headless utility VM. A supported Ubuntu Server LTS ISO is also fine. The guest ISO is different from the Proxmox installer ISO you used to install the host.
- Download the current Debian amd64 netinst ISO from the Debian project and verify its published checksum if available.
- In the Proxmox web UI, expand your node, select local (or whichever storage is configured for ISO images), then open ISO Images.
- Choose Upload and select the Debian ISO. Alternatively use the supported Download from URL option with the official download URL.
- Confirm that the ISO appears in the list. If it does not, check that the selected storage permits the ISO image content type.
Keep installation ISOs on storage intended for that purpose. Filling the host root filesystem with many large ISO images can interfere with updates and logs. Delete obsolete ISOs after a successful installation if you no longer need them, or store them on an appropriately sized directory/NAS share.
Create Your First Debian VM: A Safe Baseline Configuration
Select Create VM at the top right. The following is a deliberately modest, repeatable configuration for a small Debian server. It is a starting allocation, not a benchmark or claim that every workload needs exactly these resources. Leave sufficient RAM for Proxmox itself and any existing guests.
| Wizard page | Suggested first-VM setting | Reason / caveat |
|---|---|---|
| General | VM ID 101, name debian-lab | Any unused VM ID works; name by role. |
| OS | Choose uploaded Debian amd64 ISO | Select Linux guest type; use the current guest kernel family if asked. |
| System | Modern machine type and default/compatible firmware; q35 is a sensible modern option | SeaBIOS and OVMF/UEFI are alternatives; use one compatible with the selected guest and its boot disk. |
| Disks | 32 GiB virtual disk on suitable VM storage, SCSI with VirtIO SCSI single controller | Paravirtualised storage is efficient for current Linux; 32 GiB is enough for a light lab OS, not a data server. |
| CPU | 1 socket × 2 cores, default CPU type initially | Enough for a small utility guest; host can oversubscribe idle vCPUs, but busy guests still contend. |
| Memory | 2048 MiB to start | Use 4096 MiB if the selected packages/services require it and the host has capacity. |
| Network | Bridge vmbr0, model VirtIO | Guest receives a normal LAN connection if the switch/router permit it. |
| Options after creation | Enable QEMU Guest Agent after installing its guest package | Allows cleaner guest management; enabling the checkbox alone does not install the service inside Debian. |
On an 8 GB host, a 2 GB Debian VM leaves room for the hypervisor and perhaps one other light service. On a 16 GB host, you have more flexibility, but memory should still be budgeted for all active guests and host caches. Avoid allocating the entire physical RAM total to VMs. Virtual CPU counts are not a direct reservation of physical cores; memory pressure is usually less forgiving than light CPU oversubscription.
Choose the VM disk storage carefully. With a default ext4/LVM-thin installation, the local-lvm pool normally holds VM disks, while local holds the ISO. Do not create the VM disk on a small local root directory merely because its name looks simpler. On ZFS installs, the appropriate VM pool may have a different label.
Install Debian Inside the VM and Confirm Network Access
- After finishing the wizard, select the new VM, click Start and open its Console.
- Run the Debian installer. Use the VM’s virtual disk as the installation target; this is not the physical Proxmox host SSD. The Debian installer should see the VirtIO SCSI disk with current Linux kernels.
- For a basic LAN, accept DHCP initially if your network supplies it. Record the VM’s assigned IP from the installer or router. If you need a fixed guest address later, use a DHCP reservation or configure the guest carefully.
- Install a minimal server environment and SSH server if you need remote administration. Create a non-root user with a strong password or SSH key.
- When installation finishes, detach the ISO from the VM’s virtual CD/DVD drive (or adjust boot order), then reboot the guest from its virtual disk.
- Log in to Debian and verify DNS, package updates and basic connectivity before installing other services.
ip -br address
ip route
ping -c 3 192.168.10.1 # replace with your LAN gateway
ping -c 3 debian.org
sudo apt update
sudo apt upgradeIf the guest gets an IP but cannot reach the Internet, do not immediately reconfigure the Proxmox host. First verify the VM’s virtual NIC is attached to vmbr0, the guest has a default route, DNS resolves and the upstream network accepts another device. In a network with MAC filtering, client isolation or VLAN rules, bridging alone does not grant unrestricted access.
Install and Enable the QEMU Guest Agent
The QEMU guest agent is a service installed inside the VM. It helps Proxmox obtain guest information, request graceful shutdowns and coordinate filesystem freeze/thaw for supported backup operations. It is not the same as installing the QEMU hypervisor packages inside Debian. Do not claim backup consistency is guaranteed for every database merely because the agent is running; application-aware backups may still be necessary.
sudo apt update
sudo apt install qemu-guest-agent
sudo systemctl enable --now qemu-guest-agent
systemctl status qemu-guest-agent --no-pagerIn Proxmox, select the VM → Options → QEMU Guest Agent and enable it. If the guest agent device was not present when Debian booted, perform a full VM shutdown and start so the virtual channel appears. Then check the VM summary and guest-agent status. If the agent is inactive, inspect systemctl status inside Debian and verify that the Proxmox option is enabled.
For a first VM, you can leave advanced memory ballooning, PCI passthrough, CPU pinning, NUMA, hugepages and custom network firewall rules at defaults. Make one change at a time and keep a working restore point. More knobs do not automatically make a small home server faster or safer.
Set Up Backups Before You Put Real Data in the VM
A snapshot on the same SSD is a convenient short-term rollback point, not a replacement for backup. If the SSD dies, the host and its local snapshots may disappear together. Use Datacenter → Backup to schedule guest backups to storage configured for the VZDump backup file content type. Ideally that target is a separate NAS, a removable drive that is rotated offline or a dedicated backup server. For important services, keep another independent copy away from the mini PC.
- Add or verify a backup destination under Datacenter → Storage, checking that it supports backup content and has enough capacity.
- Run one manual backup of VM 101 from its Backup tab, choosing a suitable mode and compression.
- Schedule recurring backups and sensible retention under Datacenter → Backup. Set notifications so failures are visible.
- Perform a test restore to a different unused VM ID with networking disabled initially if a duplicate IP/hostname would be dangerous.
- Document how to reinstall Proxmox and restore the guest if the mini PC SSD fails. Protect passwords, encryption keys and the backup destination separately.
Proxmox’s official VZDump documentation explains stop, suspend and snapshot backup modes. Snapshot-mode backups minimise guest downtime but are not automatically application-consistent for every workload. The guest agent can improve filesystem consistency, while databases and transactional services may require their own quiescing or export procedure. See our mini PC plus NAS versus NAS-only guide for the architecture decision behind separate compute and backup storage.
Mini PC Proxmox Setup: Common Problems and How to Diagnose Them
| Problem | What to check | Avoid this mistake |
|---|---|---|
| Installer does not boot | USB written as a disk image; firmware boot menu; USB port; downloaded checksum | Do not assume copying the ISO file to a FAT32 stick creates a bootable installer. |
| Black screen in graphical installer | Try installer terminal mode; check display/HDMI and BIOS graphics settings | Do not repeatedly erase the SSD without first confirming the installer can run. |
| No usable SSD detected | Firmware storage mode, physical SSD, NVMe/SATA slot compatibility | Do not change storage controller settings blindly if an existing OS must be preserved. |
| Web UI unreachable | Use host console to check IP/prefix, cable, selected NIC and gateway | Do not forward TCP 8006 to the public Internet to “fix” local access. |
| Host reachable, VM no DHCP | Confirm vmbr0, VirtIO NIC, guest network and switch/VLAN policy | Do not put a second IP on the physical bridge port without understanding Linux bridges. |
| VM cannot boot after install | Remove guest ISO, check boot order and BIOS/UEFI mode | Do not change SeaBIOS ↔ OVMF without understanding the guest bootloader. |
| VM disk storage full | Inspect pvesm status, thin pool and ISO/backups | Do not treat thin provisioning as unlimited real disk space. |
| QEMU agent not running | Enable in VM Options and install/start service in guest; cold start if needed | Do not install host QEMU packages in the guest instead of qemu-guest-agent. |
| No package updates | Check host DNS, route, repo selection and subscription status | Do not paste outdated Debian/Proxmox repo lines from another major version. |
| USB device disappears after reboot | For future passthrough, inspect USB mapping and power-saving behaviour | Do not assume /dev/ttyUSB0 is a stable identifier. |
If a network change locks you out, connect a monitor and keyboard and inspect ip -br address, ip route and the Linux bridge configuration on the host. Do not paste a replacement /etc/network/interfaces file from a forum post: interface names, VLANs and bridge ports are specific to your hardware. On a remote-only host, plan a rollback method before changing networking.
If the host is unstable under sustained VM loads, inspect temperature, power supply, fan behaviour, SSD thermal throttling and memory pressure. An N100 or Ryzen mini PC can be perfectly capable of light 24/7 work without being a rack server with redundant power and out-of-band management. Its firmware and cooling still determine whether it is suitable for the workload you assign.
Security and Reliability Checks for an Always-On Home Lab
- Keep management private: no direct Internet port forwarding to Proxmox TCP 8006 or SSH; use trusted LAN/VPN access.
- Update the host and guests: apply Proxmox security updates and maintain the guest operating systems independently.
- Separate administrative access: create named users with appropriate roles where useful, enable two-factor authentication, and avoid sharing root credentials.
- Watch free space and health: check SSD SMART/NVMe status, thin-pool free space and backup failures; do not wait for a full disk to interrupt VMs.
- Protect power: a compatible UPS is useful for the mini PC, router and backup storage; plan orderly shutdown where supported.
- Keep recovery independent: back up VM data off-host and retain a short written record of network settings, storage pools, backup destination and restore steps.
A mini PC running several smart-home services can become critical household infrastructure. That is a reason to prefer predictable restart behaviour, accessible backups and a simple network plan over an elaborate configuration that only its original builder understands.
What Does a First Proxmox Mini PC Actually Cost?
Proxmox VE itself is open source and can be used without a paid support subscription. The real ownership cost is the complete mini PC, RAM, SSD, networking, backup destination, power protection, electricity and occasional replacement parts. The table below is a worksheet, not a set of live retail prices or a promise that every host draws the same watts. Enter current UK/EU quotations for the exact SKU you intend to buy.
| Cost element | Beginner one-SSD lab | Expandable multi-VM lab |
|---|---|---|
| Mini PC / barebones chassis | Entry x86-64 model with suitable virtualisation firmware | Model with two memory slots, more cores and expansion headroom |
| RAM | 8–16 GB installed, within model-supported limit | 32–64 GB or more only if officially supported by exact model/BIOS |
| SSD | 256–512 GB quality SSD | 500 GB–2 TB or multiple SSDs, depending on guest workloads |
| Network | Existing Gigabit switch/cable | 2.5GbE switch/NIC only if workloads justify it |
| Backup | Rotated external drive or existing NAS | Separate NAS/backup server plus off-site copy |
| Power protection | UPS shared with router if appropriate | UPS sized for host, switch and storage |
| Support/software | Proxmox VE community/no-subscription repository | Optional paid Proxmox subscription if support/repository assurance is required |
| Electricity | Measure whole-system average watts at the wall | Measure host plus any added switch/NAS/UPS losses |
Use the following transparent power formula. At an illustrative electricity price of £0.25/kWh—not a claimed current tariff—a host averaging 15 W uses 131.4 kWh/year and costs £32.85/year; a 35 W host uses 306.6 kWh/year and costs £76.65/year. The difference is £43.80 per year or £219 over five years. These are arithmetic scenarios, not measurements of any particular mini PC or Proxmox configuration.
Annual kWh = measured average watts × 8,760 ÷ 1,000
Annual cost = annual kWh × your actual £/kWh tariff
Five-year total = hardware + upgrades + backup + UPS + network +
(5 × annual electricity) + expected replacementsA more complete worked budgeting method is to obtain the current price for your exact mini PC and RAM/SSD bundle, add any missing memory and storage, include the independent backup and UPS, then multiply the measured whole-system average watts by your local tariff. Compare two builds only when they offer comparable RAM, usable storage, resilience and recovery. A £150 barebones PC is not a £150 functioning home server if it still needs memory, SSD, power protection and backup.
The economic decision is often simple: if you will run only one Home Assistant installation, use direct HAOS and avoid a hypervisor layer. If you already own a suitable mini PC and want two or three isolated services, Proxmox may add useful flexibility with no software licence purchase. If you are buying new hardware for a large collection of VMs, memory capacity and backup design matter more than the cheapest initial enclosure price.
What to Do Next After Your First VM Works
Once the Debian VM can reboot, reach the LAN, install updates and restore from a backup, you have a usable foundation. Then add one service at a time. For a smart-home deployment, the next decision is whether to import the official Home Assistant OS KVM image as a separate VM or use an existing Linux VM for Docker. Our Zigbee and Thread USB passthrough guide covers radio assignment separately; it is intentionally outside this basic installation walkthrough.
Record the final management IP, hostname, SSD layout, bridge name, VM ID, backup schedule and recovery method. That one-page record will save more time during a failed update or power incident than an extra CPU benchmark point. For the first week, watch RAM utilisation, host and guest disk free space, failed backups and unexpected restarts before increasing workload density.
Frequently Asked Questions
Can I install Proxmox on an Intel N100 or N150 mini PC?
Yes, provided the particular x86-64 machine exposes compatible virtualisation firmware and Proxmox has drivers for its storage and network devices. It is well suited to a small learning lab and a few modest guests. The model’s RAM limit, cooling and storage options are more important than the CPU label alone. Check exact BIOS and Linux hardware support before purchase.
Does Proxmox require two Ethernet ports?
No. A single wired Ethernet port can carry both host management and guest traffic through vmbr0. Additional NICs become useful for separate management, storage or firewall networks, but are not required for the first VM. Avoid bridging ordinary Wi-Fi as though it were a wired Ethernet interface.
Should I choose ZFS instead of ext4 on a single SSD?
Usually not for a first, uncomplicated mini-PC installation. ext4 with LVM-thin is a reasonable baseline and consumes fewer operational resources. ZFS offers valuable features, but a single-disk ZFS pool provides no drive redundancy and needs careful memory and storage planning. Choose ZFS because you understand its benefits and trade-offs, not because it sounds more advanced.
Do I need a paid Proxmox subscription?
No for home-lab functionality: Proxmox VE can run without one. A subscription provides access to enterprise repository/support arrangements according to the purchased tier. For a non-subscribed host, configure the documented no-subscription repository and keep the system updated. Do not mistake a subscription notification for a failed installation.
Why is the Proxmox web interface on port 8006?
Port 8006 is the default HTTPS management interface. Open it using https://YOUR-HOST-IP:8006 from a trusted LAN client. If it is unreachable, check the host IP, bridge, physical NIC, route and firewall. Do not expose that port directly to the public Internet.
Can I store backups on the same SSD as my VMs?
You can store a backup archive locally for convenience if the storage allows it, but it will not protect against that SSD or mini PC failing. For meaningful recovery, keep a copy on separate storage and test restoring it. Snapshots and mirrored disks are useful but do not replace independent backups.
Official Documentation and Further Reading
- Proxmox VE ISO downloads and published checksums — verify current x86-64 installer version and checksum.
- Proxmox VE hardware requirements — host RAM, CPU virtualisation, storage and passthrough prerequisites.
- Proxmox VE getting started — official bare-metal installation path and disk-erasure warning.
- Proxmox VE 9.x administration guide — authoritative storage, network, VM and package-management detail.
- Proxmox backup documentation source — current VZDump modes, consistency and scheduling.
- Debian official network installer — guest OS image for the first VM.
Editorial note: Instructions and version references were checked against official sources on 10 October 2026. Hardware examples and memory allocations are planning guidance, not a report of hands-on testing on a particular mini PC. No affiliate URLs or prices have been invented.