What problem it solves
At home or in a small workshop there’s usually one computer that runs around the clock. Lots of things go on it at once: Home Assistant, file storage, a media server, an ad blocker, a couple of servers for experiments, sometimes Windows for one program. In a single system they all get in each other’s way:
- The systems are different. Home Assistant OS is a separate OS with its own kernel, the OPNsense router is FreeBSD, Windows is Windows. They don’t fit into one Ubuntu.
- An experiment breaks the neighbors. Install a package for one service, and a library gets updated under another. Reinstalling the system wipes everything at once.
- There’s no rollback. Nobody copies the whole disk before a risky change: it takes long and needs as much space again.
Proxmox VE is a hypervisor: it splits the hardware into guests. Each guest is a separate system with its own kernel (a virtual machine) or with its own root on a shared kernel (an LXC container). Break a guest, and the neighbors keep working. Take a snapshot before an experiment, and a rollback takes seconds. At night a backup job copies every guest in full.
Everything in one system
- one OS: Home Assistant OS, OPNsense and Windows won’t sit side by side
- updating one service affects the rest
- rollback means a reinstall and restoring from memory
- a second identical server for experiments is a second computer
Everything on Proxmox
- each guest has its own system, any OS side by side
- a guest breaks — the neighbors keep working
- a snapshot before a change, rollback in seconds
- a machine for an experiment is a template clone in a minute; delete it, and there’s no trace
Who makes it and what it costs
Proxmox VE is made by Proxmox Server Solutions, an Austrian company from Vienna. It was founded by Martin and Dietmar Maurer in 2005, and the first version of Proxmox VE came out in 2008. According to the company, over 2.3 million servers ran Proxmox VE in September 2026. How it came about and what came before it — Proxmox history.
The code is open under AGPLv3, and everything is free: ZFS, clustering, high availability, backups, firewall, API. The paid subscription is per CPU socket per year. The entry tier, Community, is about €120 as of October 2026. The money buys two things:
- The
pve-enterpriserepository. Packages get there after they’ve run inpve-no-subscription. Without a subscription, install frompve-no-subscription: the packages are the same, they just arrive earlier and are less tested (No-subscription repository). - Support. Tickets from the Basic tier up: from three a year with a reply within a business day.
Without a subscription a No valid subscription pop-up appears at login. Nothing else changes.
How it works: Debian, KVM, LXC and /etc/pve
Proxmox VE isn’t a system built from scratch but Debian with a set of packages. The host’s root is regular Debian:
apt, systemd, journalctl, files in /etc. Proxmox can even be installed on top of an existing Debian instead
of using the installer.
hardware CPU with VT-x or AMD-V, memory, disks, network cards
└─ Debian 13 "trixie": apt, systemd, /etc
├─ kernel Proxmox's own, based on the Ubuntu kernel; 7.0 in 9.2, with KVM and ZFS inside
├─ QEMU + KVM virtual machines: own kernel, any OS
├─ LXC containers: the host's kernel, Linux only inside
├─ /etc/pve pmxcfs: guest and host configs; in a cluster, shared by all nodes
├─ storage local, local-lvm, ZFS, NFS, SMB, Ceph, Proxmox Backup Server
├─ network Linux bridges (vmbr0), VLAN, bond, SDN
└─ pveproxy web UI and REST API on :8006; in the console — qm, pct, pvesm, pvesh
Three things from the diagram explain almost all of Proxmox’s behavior:
- A guest is a text file. VM 100 is described in
/etc/pve/qemu-server/100.conf, container 200 in/etc/pve/lxc/200.conf. The disk lives separately, on a storage. The config is readable by eye (Proxmox VM config). /etc/pveisn’t a regular directory. It’s thepmxcfsfile system: the data is stored in the SQLite database/var/lib/pve-cluster/config.db, and in a cluster changes spread across nodes through corosync. If thepve-clusterservice didn’t start, the directory is empty — and the UI doesn’t see a single guest.- The UI is an API client. Everything a button does is available through the REST API and in the console:
qmfor VMs,pctfor containers,pveshfor any API path. That’s why Proxmox can be driven from Terraform, Ansible and scripts (Proxmox cheat sheet).
Two kinds of guests
Virtual machine
QEMU + KVM- its own kernel: Linux, Windows, FreeBSD, Home Assistant OS, RouterOS
- isolation at the CPU level
- migration to another cluster node without stopping
- passthrough of a GPU and a disk controller
- the OS alone takes hundreds of MB of memory
LXC container
host kernel- Linux only, the kernel is shared with the host
- isolation by kernel means: namespaces and cgroups
- starts in a second; idle Debian takes tens of MB of memory
- moving to another node means a restart
- Docker inside comes with caveats
When to use which, and why Docker is better off in a VM — VM or LXC.
The Proxmox family
The company has four main products, all on Debian and under AGPLv3:
| Product | What it does | At home |
|---|---|---|
| Proxmox VE | Hypervisor: VMs, containers, storage, clustering | The core of the set |
| Proxmox Backup Server | Backup storage with deduplication: a repeat backup transfers only changed blocks. Now 4.2; since April 2026 it also writes to S3 | When there are many backups or you want them on another machine (Backups in Proxmox) |
| Proxmox Mail Gateway | A mail filter in front of a mail server: spam, viruses, quarantine. The company’s first product | Only with your own mail server |
| Proxmox Datacenter Manager | Several hosts and clusters in one window, VM migration between them. 1.0 in December 2025 | From two or three separate hosts |
Where it is now: 9.2
Proxmox VE releases a major version every two years, following Debian, with point releases in between, usually in spring and autumn. The current one is 9.2 from May 21, 2026: Debian 13.5, kernel 7.0, QEMU 11.0, LXC 7.0, ZFS 2.4. In August 2026, 9.2 also came out for ARM — for now for NVIDIA Grace and Vera servers; Raspberry Pi isn’t supported: Proxmox on ARM needs UEFI and ACPI.
| Branch | Debian | Released | Support |
|---|---|---|---|
| 9.x | 13 “trixie” | August 2025 | ongoing |
| 8.x | 12 “bookworm” | June 2023 | ended in August 2026 |
| 7.x | 11 “bullseye” | July 2021 | ended in July 2024 |
A host on 8.x no longer gets security updates: move to 9 following the Proxmox “Upgrade from 8 to 9” guide, and
before that the pve8to9 --full script shows what will get in the way. An update within a branch is apt update
and apt full-upgrade, as in the Proxmox FAQ.
Where it’s used
Home server
Home Assistant OS as a VM from the official image, Docker services in an Ubuntu VM, the media server and files in containers. One mini PC instead of three boxes.
Lab
A server for an experiment is cloned from a template (VM template with cloud-init), a snapshot before a risky change, rollback in seconds. That’s how guides get tested before a production server.
A router in a VM
OPNsense or MikroTik CHR (RouterOS) in a VM, two network cards — provider and home. The router rolls back with a snapshot like any guest.
Office
A file server, a domain controller, accounting software on Windows — on one or two servers, backed up nightly to Proxmox Backup Server.
Dedicated server
A rented server with one public address: guests on their own network behind NAT, only the proxy faces outward (Proxmox networking).
Leaving VMware
Since 2024 people have been moving here from ESXi: 8.2 added an import wizard that pulls VMs straight from an ESXi host.
Other ways to solve it
| Base | Guests | Free of charge | Strong at | |
|---|---|---|---|---|
| Proxmox VE | Debian, KVM, LXC | VMs and containers | everything; the subscription is the enterprise repository and support | ZFS, backups, clustering and a web UI in one install |
| VMware ESXi | its own VMkernel | VMs | free ESXi 8 came back in April 2025 (8.0 Update 3e): no support, not for production | the corporate standard, vCenter; a stricter hardware compatibility list |
| Hyper-V | Windows Server or Windows Pro | VMs | there’s no separate free Hyper-V Server after 2019; built into Windows Pro | Windows guests, Active Directory |
| XCP-ng | Xen | VMs | everything; the Xen Orchestra web panel — from source | a XenServer fork since 2018 |
| TrueNAS, Unraid | NAS with virtualization | VMs and Docker | TrueNAS — yes, Unraid — a paid license | disks and shares come first, VMs on the side |
| Incus | any Linux, QEMU, LXC | VMs and containers | everything | command line and cloud images; the web UI is a separate package |
| libvirt (virt-manager, Cockpit) | any Linux | VMs | everything | nothing extra; you assemble backups, snapshots and networking yourself |
| If… | Use |
|---|---|
| one computer at home, several systems needed: Home Assistant, a Docker server, Windows, experiments | Proxmox VE (Installing Proxmox) |
| disks and shares come first, one or two VMs | TrueNAS or Unraid |
| only Docker containers, one system | Ubuntu and Docker without a hypervisor (Docker) |
| VMware at work, and you want the same at home for learning | free ESXi 8 — for experiments, not for data |
| guests are mostly Windows, and there’s a Windows Server license | Hyper-V |
| the command line is enough, you want cloud images and a minimum on top | Incus |
What you get and what it costs
What you get
- Everything is free, no keys. ZFS, snapshots, scheduled backups, clustering, firewall, API work without a subscription.
- Debian inside. Monitoring, your own scripts, drivers install as on any Debian. Hardware the Linux kernel sees, Proxmox sees too: there’s no compatibility list like ESXi’s.
- Two forms of guest. A VM for any OS, a container for a Linux service that gets by on 128 MB of memory.
- Backup is built in. vzdump copies a whole guest on a schedule and deletes old copies by rules; Proxmox Backup Server adds incrementals and deduplication.
- Templates and clones. A VM from a cloud-init template is ready in a minute, with a key and an address.
- Everything is text. A guest’s config is a file in
/etc/pve, every button is an API call.
What it costs
- One host is one point of failure. The host goes down — every guest goes down. A high-availability cluster needs three nodes (or two plus a separate voting QDevice) and shared or replicated disks.
- Updating the host is on us. Without a subscription it’s
pve-no-subscription, whose packages are less tested than enterprise ones. - New concepts. Bridges, storages, thin volumes, ZFS, resource permissions. A mistake in the host network cuts off access to every guest at once, and fixing it takes a monitor and keyboard.
- It needs hardware. A CPU with VT-x, 16 GB of memory or more, an SSD. ZFS takes memory for its cache and wears out cheap SSDs faster (Hardware for Proxmox).
- The UI is dense. The ExtJS web UI shows everything, but there are a lot of settings on screen. The mobile version since 9.0 is separate, in Rust, and does less.
Where to start
- Proxmox VE: what it is, who makes it and who needs it at home
- Where Proxmox came from: virtualization before it and the road from 0.9 to 9.2What came before Proxmox — mainframes, VMware, Xen, KVM, OpenVZ — and how it got from 0.9 to 9.2.
- Hardware for Proxmox: CPU, memory, disks and network cardsA CPU with VT-x and IOMMU, how much memory, which SSDs survive ZFS and which network cards are fussy.
- Virtual machine or LXC container in Proxmox: which service goes whereHow a VM differs from an LXC container, which to use for which service and where Docker goes.
- Proxmox storage: local, local-lvm, ZFS — what lives where and what it can do
localandlocal-lvmafter install, ZFS, thin volumes, snapshots: what lives where and what it can do. - Networking in Proxmox: the vmbr0 bridge, VLANs, a private network behind NAT and the firewallThe
vmbr0bridge, VLANs, a private network behind NAT, the Proxmox firewall and network card names. - Installing Proxmox VE 9: USB stick, installer, no-subscription repository and the first updateFrom a USB stick to an updated host: installer, disk, address, the no-subscription repository.
- An Ubuntu template with cloud-init in Proxmox: a VM with a key and an address in a minuteAn Ubuntu template from a cloud image: a new VM with a key and an address in a minute.
- The first LXC container in Proxmox: Debian from a template, network, SSH by key and a directory shared with the hostA Debian container from a template: network, SSH by key, a directory shared with the host.
- Backups in Proxmox: a nightly vzdump job, retention and a restore checkA nightly vzdump job, how many copies to keep and how to check a restore.
- A Proxmox virtual machine config line by line: /etc/pve/qemu-server/111.confThe VM file in
/etc/pveline by line: what each one means and what to change in it. - Proxmox day to day: qm, pct, pvesm, vzdump and logs
qm,pct,pvesm,vzdumpand logs for every day.
If it doesn’t work
apt update complains: 401 Unauthorized from enterprise.proxmox.com
- Cause
- After install the enterprise repositories are enabled — Proxmox VE and Ceph. They open only to a host with a subscription key.
- Fix
- Turn off both enterprise repositories and turn on
pve-no-subscription: node › Updates › Repositories (No-subscription repository).
A No valid subscription pop-up at every login
- Cause
- That’s how the web UI reminds you about the subscription. The pop-up doesn’t affect the host or the guests.
- Fix
- Close it with OK. Scripts that remove the pop-up by patching
proxmoxlib.jswork until the next update of theproxmox-widget-toolkitpackage.
A VM doesn’t start: KVM virtualisation configured, but not available
- Cause
- Hardware virtualization is off in the BIOS (Intel VT-x, SVM on AMD), or Proxmox itself runs in a virtual machine without nested virtualization.
- Fix
- Enable VT-x or SVM in the BIOS. Check on the host:
grep -cE 'vmx|svm' /proc/cpuinfo— a number above zero (Hardware for Proxmox).
http://address:8006 doesn’t open
- Cause
- The web UI works only over HTTPS, with a self-signed certificate.
- Fix
- Open
https://address:8006and accept the browser warning. The host address is shown on its console above the login prompt.
Almost all host memory is in use, though VMs were given less than half
- Cause
- ZFS keeps its ARC cache in memory. Since 8.1 the installer limits it to 10 % of memory but no more than 16 GiB; hosts installed earlier have no limit. The cache gives memory back under load, but the UI shows it as used.
- Fix
- How much the cache takes —
arc_summary -s arc. The limit iszfs_arc_maxin/etc/modprobe.d/zfs.conf(Proxmox storage).
After a kernel update the host dropped off the network
- Cause
- The new kernel named the network card differently, while the
vmbr0bridge in/etc/network/interfacesrefers to the old name. - Fix
- From a monitor and keyboard:
ip -br linkshows the new name; fixbridge-portsonvmbr0and runifreload -a. To keep it from happening again, pin the names (Proxmox networking).