The Intel N100 quietly became the homelab community's favorite processor. For under $200, these tiny machines pack four Alder Lake-N efficiency cores, Intel UHD Graphics, dual 2.5GbE ports (on most models), and a 6-watt TDP that lets them run 24/7 without a dent in your electricity bill. Pair one with Proxmox VE and you have a capable hypervisor that fits in your palm.

This guide walks through everything from BIOS configuration to workload recommendations, including a few gotchas specific to N100 hardware that can bite you if you go in blind.

Why the Intel N100 for Proxmox?

Before diving into setup, it's worth understanding what makes the N100 a compelling Proxmox host rather than just a capable desktop chip.

TDP: 6W base (up to ~20W under load). Running 24/7 for a year costs roughly $10–15 in electricity.
RAM: Supports up to 16GB DDR5 or DDR4 depending on the platform. Most mini PCs ship with 16GB soldered or via SODIMM.
PCIe: One NVMe M.2 slot (PCIe 3.0 x4) on most models, sometimes a second SATA M.2.
iGPU: Intel UHD Graphics (24 EU) with QuickSync — usable for hardware transcoding in Jellyfin or Plex VMs.
Network: Many N100 mini PCs ship with dual Intel i226-V or Realtek 2.5GbE NICs, which is great for homelab routing.

Popular N100 mini PC models include the Beelink EQ12 Pro, Minisforum UN100P, GMKtec NucBox M5, and ASUS NUC 14 Essential. The setup steps below apply to all of them with minor variations.

What You'll Need

An Intel N100 mini PC (8GB RAM minimum, 16GB recommended)
A USB drive (8GB+) for the Proxmox installer
A monitor and keyboard for the initial setup (or an IP-KVM if you're fancy)
A wired Ethernet connection
Balena Etcher or dd to write the installer image

BIOS Configuration Before You Install

This is where N100 setups most commonly go wrong. Spend five minutes in the BIOS before touching the installer.

Enter the BIOS

Most N100 mini PCs use Delete or F2 to enter the BIOS during POST. Check your model's documentation — GMKtec and Beelink both use Delete.

Critical Settings to Change

Virtualization (VT-x / VT-d): This is almost always disabled by default on budget mini PCs.

Enable Intel Virtualization Technology (VT-x) — required for KVM.
Enable Intel VT-d — required for PCIe passthrough (including iGPU).

Look under Advanced → CPU Configuration or Advanced → System Agent Configuration depending on your BIOS.

Secure Boot: Disable Secure Boot. Proxmox's GRUB bootloader does not require it and leaving it on can cause boot failures, especially with older installer ISOs.

Boot Order: Set your USB drive as the first boot device. After install, flip this back to your NVMe to avoid accidental reinstalls.

SR-IOV (if available): Some N100 boards expose an SR-IOV setting for the i226-V NIC. Leave this disabled for now — you can revisit it if you want to share the NIC across VMs later.

Power Settings: Set the AC power recovery to Last State or Power On. This ensures your Proxmox node comes back up automatically after a power cut.

iGPU Memory Allocation: If you plan to use the integrated GPU for transcoding or passthrough, look for DVMT Pre-Allocated under graphics settings and bump it from 32MB to 256MB or higher.

Installing Proxmox VE

Download the latest Proxmox VE ISO from the official site (8.x as of 2026). Write it to a USB drive:

# Linux/macOS
dd if=proxmox-ve_8.x-1.iso of=/dev/sdX bs=4M status=progress

Or use Balena Etcher on Windows

Boot from the USB, select Install Proxmox VE (Terminal UI) for reliability on N100 hardware, and work through the installer:

Accept the EULA.
Select your NVMe as the target disk. Use ext4 for simplicity or ZFS RAID0 if you want built-in checksumming on a single drive.
Set your country, timezone, and keyboard layout.
Configure the management IP — use a static address. Pick something outside your DHCP range (e.g., 192.168.1.10/24).
Set a strong root password and a valid email address for alert notifications.
Confirm and let the installer run. It typically takes 3–5 minutes on NVMe.

Remove the USB when prompted and let the system reboot.

Post-Install: First Steps

SSH into your node or open a browser to https://<your-ip>:8006 and log in as root.

Switch to the No-Subscription Repository

The default Proxmox install points to the enterprise repository, which requires a paid subscription. For homelab use, switch to the community repo:

# Remove the enterprise repo
rm /etc/apt/sources.list.d/pve-enterprise.list

Add no-subscription repo

echo "deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription" \

/etc/apt/sources.list.d/pve-no-subscription.list

Also handle the Ceph repo if present

sed -i 's/enterprise/no-subscription/g' /etc/apt/sources.list.d/ceph.list 2>/dev/null || true

apt update && apt dist-upgrade -y

Dismiss the Subscription Nag (Optional)

If the "No valid subscription" popup bothers you:

sed -Ezi.bak "s/(Ext.Msg.show\(\{\s+title: gettext\('No valid subscription'\))/void\(\{ \/\/\1/g" \
  /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
systemctl restart pveproxy

Update the Kernel

N100 (Alder Lake-N) launched after many Linux kernel stable releases. Proxmox 8.x ships with kernel 6.5+ which has solid N100 support, but upgrading to the latest available kernel improves thermal management and i226-V NIC stability:

apt install pve-kernel-6.8 -y
# Or install the latest from pve-kernel-*
update-grub
reboot

After reboot, verify:

uname -r
# Should show 6.8.x-x-pve or newer

Fixing the Realtek 2.5GbE NIC (If Applicable)

Some N100 mini PCs ship with a Realtek RTL8125 instead of Intel i226-V. The r8169 driver included in the kernel is functional but has stability issues under high load. Install the vendor driver:

apt install r8168-dkms -y
reboot

Verify the correct module is loaded:

lsmod | grep r8168
ethtool -i enp1s0 | grep driver
# Should show r8168, not r8169

If you have Intel i226-V NICs, no extra drivers are needed — the kernel handles them natively.

Enabling IOMMU for Passthrough

For iGPU passthrough or any PCIe device passthrough, you need IOMMU enabled at the kernel level. On N100 systems with VT-d enabled in BIOS:

# Edit GRUB
nano /etc/default/grub

Find the line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet"

Change it to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"

Save, then:

bash update-grub reboot

Verify IOMMU is active:

dmesg | grep -e DMAR -e IOMMU
# Look for: DMAR: IOMMU enabled

Check your IOMMU groups:

for d in /sys/kernel/iommu_groups/*/devices/*; do
  n=${d#*/iommu_groups/*}; n=${n%%/*}
  printf 'IOMMU Group %s ' "$n"
  lspci -nns "${d##*/}"
done

For iGPU passthrough, the GPU and its audio device should ideally be in their own IOMMU group. N100 iGPU behavior here varies by board — some place the iGPU cleanly in its own group, others bundle it with other devices.

Configuring Storage

Single NVMe Setup

For a single-disk homelab node, the simplest layout is:

Proxmox OS on the NVMe (installed by the installer)
Local-LVM for VM disks (created automatically)
A directory storage for ISO images and container templates

This is what you get by default. No changes needed.

Adding ZFS on a Second Drive

If your mini PC has a second M.2 slot (many do), add a SATA or NVMe SSD there and create a ZFS pool for extra storage:

# Identify the disk
lsblk

Create a ZFS pool (single disk, no redundancy)

zpool create -f -o ashift=12 tank /dev/sdb

Add it to Proxmox storage

pvesm add zfspool tank-storage --pool tank --sparse 1

ZFS gives you snapshots, compression, and data integrity checksums — valuable even on a single disk for a homelab.

Ideal Workloads for N100 Proxmox Hosts

The N100 is capable but bounded. Here's what it handles comfortably:

Works Great

Home Assistant OS VM — Runs excellently. Allocate 2 vCPUs and 2GB RAM.
Pi-hole or AdGuard Home LXC — Tiny footprint, runs in an 256MB LXC container.
Nginx Proxy Manager LXC — Handles dozens of reverse-proxied services with ease.
Jellyfin with hardware transcoding — The iGPU's QuickSync handles simultaneous 4K→1080p transcode streams. One or two concurrent streams is no problem.
Nextcloud AIO — Runs well in a Docker LXC or dedicated VM with 4GB RAM.
Wireguard VPN LXC — Negligible CPU load, runs in 128MB.
Uptime Kuma, Vaultwarden, Gitea — All lightweight self-hosted apps thrive here.

Proceed with Caution

Multiple Windows VMs simultaneously — Windows 11 wants 4GB RAM minimum per instance. With 16GB total, you can run two comfortably but watch memory pressure.
Kubernetes (k3s/Talos) with heavy workloads — The N100 can run a 3-node k3s cluster but CPU-intensive pods may feel sluggish.
Database-heavy stacks — Postgres and MySQL are fine; memory-hungry analytics workloads less so.

Avoid

Full GPU-intensive AI inference — The 24 EU iGPU can run small GGUF models via Ollama but don't expect Llama 3 70B performance.
Anything needing more than 16GB RAM — The N100's memory ceiling is a hard constraint.
High-throughput NFS/Samba servers — The N100's single PCIe 3.0 x4 NVMe slot is a bottleneck for NAS workloads. This is a hypervisor, not a dedicated NAS.

Performance Tuning for the N100

CPU Scaling Governor

The N100 defaults to powersave governor in Linux, which throttles performance. For a server that needs consistent responsiveness:

apt install cpufrequtils -y
cpufreq-set -r -g performance

Make it persistent

echo 'GOVERNOR="performance"' > /etc/default/cpufrequtils systemctl enable cpufrequtils

Alternatively, use schedutil for a balance between power and performance:

cpufreq-set -r -g schedutil

Memory Balloon and Hugepages

For VMs that need consistent low-latency memory access (databases, Jellyfin), disable memory ballooning in the VM options and consider enabling hugepages:

# Add to /etc/sysctl.conf
vm.nr_hugepages = 512

sysctl -p

Thermal Monitoring

N100 mini PCs can throttle under sustained load due to aggressive thermal limits. Monitor temperatures:

apt install lm-sensors -y
sensors-detect --auto
sensors

Typical operating temperatures under load are 60–75°C. If you're seeing 85°C+ and CPU throttling, consider reapplying thermal paste on the die (common on budget units) or ensuring adequate ventilation.

Setting Up the Proxmox Firewall

Even in a homelab, locking down the management interface is good practice:

# Enable the Proxmox datacenter firewall
pvesh set /cluster/firewall/options --enable 1

Allow management access only from your LAN

pvesh create /cluster/firewall/rules --action ACCEPT --type in
--proto tcp --dport 8006 --source 192.168.1.0/24 --enable 1

Allow SSH from LAN only

pvesh create /cluster/firewall/rules --action ACCEPT --type in
--proto tcp --dport 22 --source 192.168.1.0/24 --enable 1

Or configure it via the web UI under Datacenter → Firewall.

Monitoring Your N100 Node

Add a simple resource monitoring view in the Proxmox UI by navigating to your node and opening the Summary tab. For more detailed metrics, consider the InfluxDB integration built into Proxmox:

Datacenter → Metric Server → Add → InfluxDB

Or if you're running a Grafana/Prometheus stack elsewhere in your homelab, install the node_exporter directly:

apt install prometheus-node-exporter -y
systemctl enable --now prometheus-node-exporter

This exposes metrics at http://<node-ip>:9100/metrics for scraping.

Conclusion

The Intel N100 mini PC is one of the most cost-effective Proxmox hosts you can buy in 2026. For $150–200 you get a node that sips power, runs a dozen or more lightweight services simultaneously, and handles hardware transcoding — all in a form factor smaller than a paperback book.

The key steps that make or break an N100 Proxmox setup are the BIOS tweaks (VT-x, VT-d, iGPU memory), the repository switch to the community edition, and the kernel update for full Alder Lake-N support. Get those right and the rest of the install is smooth sailing.

If you're building out a homelab in 2026 and don't need GPU-accelerated AI or massive RAM, a pair of N100 mini PCs running a two-node Proxmox cluster with shared storage covers the vast majority of homelab use cases at a fraction of the cost and power draw of enterprise hardware.