Skip to content

Proxmox VE

Debian-based open-source virtualization platform unifying QEMU/KVM virtual machines and LXC system containers under one web UI, with clustering, high availability, software-defined storage (ZFS, Ceph), SDN, and integrated backup — the default landing zone for the post-VMware private-virtualization exodus.

Overview

Proxmox Virtual Environment (PVE) is developed by Proxmox Server Solutions GmbH (Vienna). It turns commodity x86-64 or arm64 servers into a hypervisor cluster managed through an integrated stack: web GUI (port 8006), CLI (qm, pct, pvesh, pvecm), and a REST API. Everything lives in the same package set — no separate management appliance. Current release: PVE 9.2 (May 21, 2026; arm64 variant Aug 5, 2026) on Debian 13 Trixie with kernel 7.0, QEMU 11.0, LXC 7.0, ZFS 2.4, and Ceph Squid 19.2.3 / Tentacle 20.2.1.

Evaluation

  • Why it's better: One product covers the whole stack competitors split across projects: hypervisor + cluster + HA + scheduler (CRS), hyperconverged Ceph, ZFS replication, incremental deduplicated backup (Proxmox Backup Server), SDN with EVPN/WireGuard/BGP fabrics, and RBAC/OIDC identity — all under AGPLv3 with all features free, forever, no feature gates per subscription tier.
  • When it fits: On-prem private cloud and homelab alike: VM + container consolidation, VMware vSphere replacements (native ESXi import wizard), hyperconverged 3-6 node clusters with Ceph, GPU passthrough for AI workloads (NVIDIA vGPU supported), edge/ARM deployments (9.2 arm64), and air-gapped enterprises (offline updates on paid tiers).
  • When it does not fit: Multi-tenant public IaaS at OpenStack scale (tenancy, quota, billing); teams standardized on vSphere APIs/NSFC-vmotion ecosystems; strict per-workload commercial SLAs without budget for the support tiers (Community tier has no ticket support).
Pros Cons
AGPLv3, all features free; subscriptions only add support + Enterprise repo No official Datacenter Manager parity with vCenter for very large estates yet (PDM 1.0 shipped Dec 2025, maturing)
Unified VMs (KVM) + LXC containers, templates/linked clones, live migration Cluster file system (pmxcfs) caps config at 128 MiB — thousands of VMs fine, exotic metadata not
Hyperconverged Ceph + ZFS built in; snapshots-as-volume-chain (9.x) Windows/qcow2 snapshots on file-based storage can block VMs for minutes
CRS dynamic load balancing (9.2), HA disarm/arm for maintenance Live migration restricted to same CPU vendor (and same arch x86 vs arm64)
PBS: dedup, encryption, live restore, backup fleecing, S3-capable Perl internals in gradual Rust migration; some legacy iptables firewall paths until nftables graduates
arm64 support since 9.2 (Aug 2026); ARMv9 recommended NVIDIA-only for vGPU live migration today
  • Common Use Cases: Homelab consolidation (LXC-first), enterprise VMware replacements, hyperconverged 3-node Ceph branches, VDI with GPU passthrough, backup targets via PBS, CI runners and bare-metal-style LXC, air-gapped defense/regulated deployments (offline updates).
  • Licensing & Commercial Use: AGPLv3 open source. Subscriptions are per occupied CPU socket (cores irrelevant), all nodes in a cluster at the same level: Basic EUR 370 / Standard EUR 550 / Premium EUR 1,100 per socket-year (support tiers), Community EUR 120 (Enterprise repo access, no tickets), or the free no-subscription repo. See Reference for the full matrix.
  • Ecosystem & Data Connections: Proxmox Backup Server (dedup backup), Proxmox Datacenter Manager (multi-site rollup, 1.0 Dec 2025), Terraform/OpenTofu + Ansible providers, REST API + API tokens, community helper-scripts ecosystem, NetBox/phpIPAM/PowerDNS IPAM/DNS plugins (SDN, tech preview).
  • Compatibility & Requirements: 64-bit x86 (Intel VT / AMD-V) or arm64 (ARMv8-A min, v9 recommended); IOMMU (VT-d/AMD-Vi/SMMU) for passthrough; ~2 GB RAM for the OS + guest RAM; ZFS/Ceph ~1 GB RAM per TB used storage. See Reference.
  • Latest Versions: PVE 9.2 (x86 May 21, 2026; arm64 Aug 5, 2026), PBS 4.2 (Apr 29, 2026), PDM 1.0 (Dec 4, 2025). Roadmap: snapshots-as-volume-chain GA on more storages, nftables firewall graduation, LUKS root encryption in installer, OCI/Compose app deployment for LXC groups.
  • Alternatives: OpenNebula (topic) and OpenStack (topic) for cloud-style orchestration; XCP-ng + XO; Harvester (k8s-native); oVirt/RHV (discontinued); the incumbent being migrated away from: VMware vSphere.
  • Migration & Lock-in Risks: Config in plain text under /etc/pve (pmxcfs) + open API — exit paths are real (qcow2/zvol images are portable; PBS backups restorable anywhere with the key). Lock-in is low; the bigger risk is corosync cluster design (see How-to guides).
  • Community Health: Very active: forum + pve-user list, HN regular (9.0 release 190 points; ESXi import 245; helper scripts 238; PDM 1.0 183), large third-party script/library ecosystem, enterprise adoption growing since the Broadcom/VMware licensing shock of 2024.

Position in the Landscape

The private-virtualization field sorts by ambition: PVE owns the "hypervisor appliance" layer (per-node simplicity, cluster of 3-50 nodes); OpenNebula adds cloud-style self-service and federation without OpenStack's weight; OpenStack stays the answer for genuine multi-tenant IaaS with quotas, billing, and many teams. PVE's bet is that most "private cloud" demand is really a well-run hypervisor cluster plus good backups — the 2024-2026 VMware migrations validated that bet operationally, and the Datacenter Manager + "Cattle and Pets" roadmap is how it defends the upper end.

Notes In This Folder

  • How-to guides — install, repos, VMs/CTs, clustering, Ceph, PBS backups, passthrough, SDN, troubleshooting
  • Reference — versions, pricing, requirements, ports, repos, storage matrix
  • Explanation — pmxcfs/corosync internals, HA/CRS, SDN, backup pipeline, threat model

Sources

All URLs verified HTTP 200 on 2026-09-25.

Questions

  • How far has PDM matured past 1.0 for multi-cluster estates (TBD — track pdm.proxmox.com changelog)?
  • When do snapshots-as-volume-chains leave tech preview on Directory/NFS/CIFS, and when does replication extend beyond ZFS? (roadmap: in progress)
  • Does the nftables firewall reach feature parity with the legacy iptables stack? (roadmap: graduation planned)
  • Real-world CRS load-balancer behavior on 50+ node clusters — community data still thin (TBD).