Skip to content

Reference

Context

Look-up facts: current versions, release history, subscription pricing, system requirements, network ports, repository definitions, the storage capability matrix, and hard limits.

Current Versions (September 2026)

Product Version Released Base
Proxmox VE 9.2 (x86-64) 2026-05-21 Debian 13.5 Trixie, kernel 7.0, QEMU 11.0, LXC 7.0, ZFS 2.4
Proxmox VE 9.2 (arm64) 2026-08-05 Same userspace; ARMv8-A min, ARMv9 recommended
Proxmox Backup Server 4.2 2026-04-29 Dedup chunk store, S3 datastores (4.0+)
Proxmox Datacenter Manager 1.0 2025-12-04 Multi-cluster rollup management
Ceph (integrated) Squid 19.2.3 / Tentacle 20.2.1 with PVE 9.2 Tentacle available as stable option

Release History (recent majors)

Release Date Notable
PVE 9.0 2025-08-05 Debian 13 base; snapshots-as-volume-chain tech preview; mobile UI
PVE 9.1 2025-11-19 Ceph Squid 19.2.3; mobile UI improvements; 8.4 seamless upgrade
PVE 9.2 2026-05-21 CRS dynamic load balancing; SDN fabrics (WireGuard/BGP); custom CPU models in GUI; disarm-ha/arm-ha; kernel 7.0 default; Ceph Tentacle option
PVE 9.2 arm64 2026-08-05 First arm64 release of the 9.x line

Subscription Pricing (per occupied CPU socket / year, net EUR)

Tier Price Support
Premium EUR 1,100 Unlimited tickets, 2h Sev-1 response, 24/7 (from Oct 19, 2026)
Standard EUR 550 10 tickets/yr, 4h Sev-1 response, 24/7 (by end of 2026)
Basic EUR 370 3 tickets/yr, 1 business-day response
Community EUR 120 Enterprise repo access, no ticket support (forum only)
No-subscription repo free Community-maintained access to the same packages, not recommended for production

Rules: subscription covers every occupied socket (core count irrelevant); every cluster node must be covered; all nodes in a cluster must use the same level. All PVE features exist at every level — tiers differ only in support and repo access. PDM is included with subscriptions. ARM64 support is sold via sales contact. Enterprise support business-hours coverage: CET/CEST Mon-Fri 07:00-17:00 (Austrian business days), with NA/APAC regional hours from Oct 19, 2026.

System Requirements

Evaluation (min) Recommended production
CPU 64-bit x86 (Intel 64/AMD64) or arm64 (ARMv8-A); VT-x/AMD-V for KVM Same; ARMv9-A on arm64
RAM 1 GB + guest RAM 2 GB for OS/services + guests; ~1 GB per TB used storage for ZFS/Ceph
Disk (installer-dependent) Fast storage; ZFS prefers direct-attached disks, plenty of RAM
Network 1 NIC Dedicated NIC for corosync; second physical link for redundancy
Passthrough — IOMMU: Intel VT-d / AMD-Vi (SMMU on arm64)

arm64 caveats: AMD SEV and Intel GVT-g are x86-only; no OS-level microcode package; live migration only between same-architecture nodes. Benchmark a node with pveperf (CPU + fsync throughput).

Network Ports

Port Protocol Service
8006 TCP Web UI + REST API (pveproxy)
22 TCP SSH (node joins, cluster ops)
5405-5412 UDP corosync cluster communication
5900-5999+ TCP VNC consoles (per guest offset)
3128 TCP SPICE proxy
60000-60050 TCP Live migration (qemu migration traffic)

Package Repositories (9.x, deb822 format)

Repo URI Component Access
Enterprise (recommended for subscribers) https://enterprise.proxmox.com/debian/pve pve-enterprise Subscription key required; stable, tested updates
No-subscription http://download.proxmox.com/debian/pve pve-no-subscription Free; same packages, wider testing risk
Ceph enterprise https://enterprise.proxmox.com/debian/ceph-<codename> enterprise Subscription
Ceph no-subscription http://download.proxmox.com/debian/ceph-<codename> no-subscription Free

Suites: trixie for PVE 9.x. Legacy single-line sources.list entries still work; new installs use /etc/apt/sources.list.d/*.sources.

Storage Type Matrix

Type Plugin Shared Snapshots Notes
ZFS (local) zfspool no yes zvols; PVE replication source/destination
Directory dir no yes (qcow2 / volume chain) any filesystem
BTRFS btrfs no yes tech preview
NFS / CIFS nfs/cifs yes yes (qcow2 / volume chain) file-based snapshots can block large VMs
LVM lvm no (unless on shared LUN) via volume chain (9+) thick
LVM-thin lvmthin no yes thin provisioning
iSCSI (kernel/libiscsi) iscsi/iscsidirect yes via LUN/volume chain multipath recommended
FC / SAS native yes via volume chain no dedicated plugin needed
Ceph RBD rbd yes yes hyperconverged or external (monhost list)
CephFS cephfs yes yes file storage on Ceph
ZFS over iSCSI zfs yes yes remote ZFS appliance
Proxmox Backup pbs yes n/a (backup target) dedup, encryption, live restore

Storage Config Examples (/etc/pve/storage.cfg)

zfspool: vmdata
        pool tank/vmdata
        content rootdir,images
        sparse

rbd: ceph-external
        monhost 10.1.1.20 10.1.1.21 10.1.1.22
        pool ceph-external
        content images
        username pve-rbd

Backup Modes (vzdump)

Mode Downtime Consistency Use
stop full highest small guests, maintenance windows
suspend brief (very old) good legacy fallback
snapshot none crash-consistent (fsfrozen on some FS) default for modern setups; PBS adds fleecing

Limits and Gotchas

  • pmxcfs config database: 128 MiB RAM-cached cap (thousands of VM configs fine).
  • corosync: up to 8 links; a single bond-backed link can mask partitions — use physically separate links.
  • Live migration: same CPU vendor recommended, same architecture required (x86 <-> arm64 impossible).
  • Choice cardinality for storage content types is per-storage (content images,rootdir,...); misconfigured content types are the #1 "cannot allocate disk" cause.
  • pvecm expected N overrides quorum — break-glass only.
  • Cluster-wide: all nodes should run the same PVE version for HA; mixed versions tolerated only during rolling upgrades.

Hardening Pointers (checklist form)

  • Management on a dedicated VLAN; 8006 + 22 reachable only from admin networks
  • 2FA (TOTP/WebAuthn) enforced on all admin realms; root login via PAM restricted
  • API tokens for automation; per-path RBAC instead of Administrator@pam everywhere
  • corosync on isolated NIC/VLAN with authkey encryption
  • PBS datastore encryption enabled for off-site; key custody documented and tested
  • Unprivileged LXC by default; nesting only where required
  • Enterprise (or Community) repo + timely updates; offline-update procedure for air-gapped sites
  • Regular restore tests (PBS live restore makes this cheap)

Sources