One afternoon Project

Building a mini PC hypervisor host, start to finish

A small, quiet mini PC running an open-source hypervisor platform is the foundation of countless homelabs, including the hosts in our Shelf Lab and Closet Lab. This project takes you from choosing the box to a hardened host with its first guests and nightly backups.

  • BeginnerDifficulty
  • 3 to 4 hoursTime, after delivery
  • 1 mini PC6 to 8 cores, 16 to 32 GB
  • $150 to $550Late 2026, 16 GB at the low end

Choosing the mini PC

Size the machine for the lab you expect to run over the next two years, not for every possible experiment. Memory runs out first.

LevelCPUMemoryStorageNetworkComfortable running
Starter4 to 6 cores16 GB500 GB SSD1 GbEDNS filtering, monitoring, home automation, a container VM
Balanced6 to 8 cores32 GB1 TB NVMe1 or 2.5 GbESeveral VMs, a container host, media and development
Advanced8 or more cores64 GB or moreTwo NVMe drives2.5 GbEMany VMs, databases, larger self-hosted stacks

Check before you buy

  • Memory sockets. Some small machines have soldered memory that can never be upgraded. Prefer two socketed slots; many models then accept 64 GB or more.
  • Storage slots. A second M.2 slot is valuable, but some models pair one NVMe slot with one slower SATA-only slot. Read the specification, not the photos.
  • Network. Wired Ethernet is essential; wireless complicates virtual networking. 2.5 GbE only helps if the switch and the machines at the other end support it too.
  • Virtualization support. Any current 64-bit processor has it, but confirm the firmware lets you enable it and the IOMMU option.
  • Know the limits. Few drive bays, few or no expansion slots, usually one network port, no management controller and limited ECC options. When you need those, you have outgrown the mini PC, which is a fine problem to have.

During the memory shortage of 2025 and 2026, refurbished business units that already include 16 or 32 GB were usually the best value. See Budgeting a Homelab.

Before installing

  1. Save anything on the machine. Installing the hypervisor erases the preinstalled operating system.
  2. Update the firmware if the vendor offers updates, then enable CPU virtualization and the IOMMU option, and set the boot order.
  3. Run a memory test overnight if the machine is used. See the used hardware checklist.
  4. Connect Ethernet, a monitor and a keyboard for the installation only.
  5. Reserve the management address. In our example network the host becomes hv01.lab.example.net at 10.42.10.11 on the management VLAN.

Installing the hypervisor platform

  1. Download the current release of the platform from its official site and write it to a USB stick. Avoid tutorials for older major versions; at least one popular platform's previous release reached end of life in 2026.
  2. Choose the target disk carefully. The installer wipes whatever you select.
  3. Set a strong administrator password, a real address for system notifications, the hostname and the management IP address.
  4. Remove the USB stick and reboot. The console then shows the address of the web interface.
  5. Log in from your workstation. Expect a certificate warning the first time, because the host uses a self-signed certificate. Confirm the address is your server's before accepting it.

First-login checklist

  • Configure the free update repository the platform provides, then install all updates and reboot.
  • Confirm the date, time and time zone, and that all CPU cores, memory and disks are detected.
  • Create a separate named administrator account with multi-factor authentication for everyday use.
  • Configure notifications so failed backups and disk errors reach you.
  • Record the platform version, network settings and disk layout in your notes.

Rule of thumb

Do not install applications on the hypervisor host itself. Everything runs in a VM or container. A host that only does virtualization is easy to update, easy to back up and easy to rebuild.

Networking

Connect the mini PC to a trunk port on your managed switch carrying your VLANs, and make the default bridge VLAN-aware. Then each guest's network card can be placed on the right VLAN with one setting: the host's own interface on management, the container host on the lab network and so on. With a single network port, this is the cleanest design. See VLANs and Segmentation.

Your first guests

  1. A template. Build a small Linux VM with your user, SSH key and automatic updates, generalize it and convert it to a template, as described in Virtualization.
  2. A container host VM. Clone the template into apps01.lab.example.net at 10.42.30.30, with 4 to 8 GB of memory, and install the container engine. Most of your services will live here.
  3. Light services as system containers, such as an uptime monitor, each with 512 MB to 1 GB of memory to start.
  4. A VM for services that need one, such as a home automation hub with a USB radio adapter passed through.

Leave memory unassigned. The host and its storage need headroom, and you will want room for experiments. Raise a guest's allocation only when monitoring shows real pressure.

Snapshots and backups

  • Snapshot before every change, and delete the snapshot once you are happy. A snapshot lives on the same disk, so it is an undo button, not a backup.
  • Schedule nightly backups of every guest to another machine, such as a share on your NAS where the host can add backups but not delete them, or a backup server that pulls them. Back up all guests in one job so new ones are never forgotten. See Backup Strategy.
  • Remember that two internal drives are one computer. A second SSD inside the mini PC is useful for scratch space, not for your only backup.
  • Restore a guest onto the host under a new ID to prove the backups work.

Verify

  • The web interface is reachable only from the management network or your VPN.
  • Each guest sits on the VLAN you intended and receives the expected address.
  • Rebooting the host brings every guest back in the right order.
  • A guest restored from last night's backup boots and works.

Keeping it healthy

  • Keep vents clear and watch CPU and SSD temperatures; small machines running 24 hours a day get warm.
  • Watch SSD wear. Hypervisors write logs constantly, and wear is easy to plan for when you track it.
  • Reach the web interface only from the management network or over your VPN, never from the internet.
  • Community scripts that create guests in one line are convenient, but they run as root on the host. Read them first.

When this host is full, add a second mini PC rather than a bigger one. Two independent hosts with good backups are more resilient than one large machine, and that is exactly how the Shelf Lab grows into the Closet Lab.