A mini PC or old laptop as a Proxmox host: sizing the box
How many Windows VMs a small host can carry, what cores and RAM to buy, and the NIC and storage choices that decide whether it is usable.
- Build
- 26300.9457 / 26100.33650
- Edition
- Pro (26H2) / Server
- Architecture
- x64
- Support
- Documentation (E1)
- Evidence
- E1Official documentation
- Verified
- 2026-10-29
- Page type
- Concept
The short answer
Section titled “The short answer”A homelab host is sized by RAM first, cores second, storage third, network fourth. Everything else is a detail.
Rules that hold up:
- RAM is the hard limit. A Windows 11 VM wants 6–8GB to be pleasant; Server Core can run in 2–4GB.
- Two vCPUs per VM is enough for most lab work; oversubscribing vCPUs raises latency.
- SSD/NVMe only. Thin-provisioned Windows VMs on spinning disks are painful.
- One NIC is fine to start; a second one makes a lab much more interesting later.
The sizing table
Section titled “The sizing table”| Host | Comfortable Windows guests |
|---|---|
| 16GB RAM, 4 cores | 1 (8GB) + a container or two |
| 32GB RAM, 8 cores | 3 (8GB each), or 2 + Server Core |
| 64GB RAM, 12–16 cores | 6–7 mixed guests |
| 96GB+ | a rack in a box |
This site’s lab is a 16-core / 31.2GB Proxmox host running two 8GB Windows 11 VMs. That fits, but with little room: a third 8GB guest needs memory freed first.
What actually matters when buying
Section titled “What actually matters when buying”| Spec | Why it matters |
|---|---|
| RAM (soldered on most mini PCs) | the limit you cannot upgrade |
| NIC | Intel i225/i226 or better; Realtek 8125 works but has quirks |
| Storage | NVMe slot count, and whether the box takes a 2.5” drive |
| CPU TDP / cooling | a 15W part is quiet but slow with 3 VMs |
| Idle power | a homelab runs 24/7; 10W vs 30W matters on the bill |
| vPro/AMT or IPMI | remote console without a monitor |
Mini PCs usually have soldered RAM and one NVMe slot. Buy the RAM capacity you will want in a year, not the one you need today.
Old laptop vs mini PC
Section titled “Old laptop vs mini PC”| Old laptop | Mini PC | |
|---|---|---|
| Cost | free if you have it | cheap |
| RAM | often upgradeable (SO-DIMM) | usually soldered |
| Storage | one SATA + maybe M.2 | one or two M.2 |
| Network | 1 GbE + Wi-Fi | 2.5GbE typical |
| Reliability | battery as a UPS (a plus) | needs its own UPS |
| Lid/thermal | clamshell cooling, dust | better airflow |
An old laptop is an excellent first host precisely because it is free and has a built-in UPS. Its weakness is one disk and one NIC.
Proxmox setup that avoids pain
Section titled “Proxmox setup that avoids pain”- Install PVE with ZFS on a single disk (or ext4/lvm-thin if RAM is tight — ZFS wants RAM).
- Create a Windows VM with
q35, OVMF, vTPM 2.0, VirtIO SCSI, VirtIO NIC. - Install VirtIO drivers during setup, or the disk list is empty.
- Use
--cpu hostif you want nested virtualisation (WSL2/Hyper-V inside the guest). - Keep a template and clone; do not reinstall Windows per experiment.
Guest sizing that works on a 32GB host: Windows 11 Pro 8GB / 4 vCPU / 64GB disk Windows Server 4GB / 2 vCPU / 40GB disk Linux service 2GB / 2 vCPU / 16GB diskPower and noise
Section titled “Power and noise”- A 15W mini PC is effectively silent; a 35–45W part with a small fan is audible in a quiet room.
- Put the host where you will not hear it, and give it airflow.
- A cheap UPS (even a small one) prevents the corruption that an unclean shutdown causes on any guest filesystem.
Related
Section titled “Related”Lab boundary
Section titled “Lab boundary”E1 for the sizing guidance (Proxmox and Microsoft documentation). The host figures quoted are this site’s lab record, not a benchmark; see the host-memory page for how they were observed.