If your Proxmox notes still stop around Proxmox VE 8.1, 8.2, or the older 2024 update path, this is the catch-up guide before you touch Proxmox VE 9. Do not treat 8.2 to 9.1 as one casual jump. The clean path is to get every node fully current on the Proxmox VE 8 line first, with 8.4 as the required staging point for the official 8-to-9 upgrade.
The missing middle matters. Proxmox VE 8.3 arrived on November 21, 2024 with Debian 12.8, kernel 6.8.12-4 as the stable default, QEMU 9.0.2, LXC 6.0.0, ZFS 2.2.6, SDN/firewall improvements, webhook notifications, Tag View, Ceph Squid preview, faster container backups, and improved OVF/OVA imports. Proxmox VE 8.4 followed on April 9, 2025 with Debian 12.10, QEMU 9.2.0, ZFS 2.2.7, Ceph Squid as a stable option, virtiofs directory passthrough, third-party backup APIs, and live migration support for mediated devices such as supported NVIDIA vGPU setups.
Before You Start
Run this from a real console, IPMI/iKVM, or SSH inside tmux or screen. For clusters, move guests away from one node, update that node, reboot, verify, then continue to the next node. Do not update every node at the same time.
tmux new -s pve84-catchup
pveversion -v
cat /etc/os-release
pvecm status 2>/dev/null || true
ha-manager status 2>/dev/null || true
ceph --version 2>/dev/null || true
zpool status 2>/dev/null || true
df -h /
If the host is still on Proxmox VE 7.x, use the older 7.4 to 8.0 upgrade path first. This guide assumes the host is already on Proxmox VE 8.x and needs to catch up to 8.4.
Check Repositories While Still On Bookworm
Proxmox VE 8 uses Debian Bookworm repositories. Clean up dead mirrors, third-party repos, or stale enterprise/no-subscription entries before the upgrade. Production hosts should use the enterprise repository when a subscription is available. Lab hosts without a subscription can use the no-subscription repository.
grep -R "proxmox\|pve\|bookworm" /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/null
apt update
apt policy pve-manager proxmox-ve
For a no-subscription lab host using deb822 repository files, the Proxmox VE 8 entry should point at Bookworm, not Trixie yet:
cat > /etc/apt/sources.list.d/proxmox.sources << 'EOF'
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: bookworm
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF
Update One Node To Latest 8.4
On a standalone host, stop or migrate anything sensitive first. On a cluster, migrate guests off the node you are touching. Then update packages, reboot into the new kernel, and verify services.
apt update
apt dist-upgrade
pveversion
reboot
After the host returns:
pveversion -v
uname -r
systemctl status pveproxy pvedaemon pvestatd pve-cluster --no-pager
pvecm status 2>/dev/null || true
ha-manager status 2>/dev/null || true
Cluster Order
For a cluster, repeat the same process node by node. Keep quorum healthy, do not leave mixed nodes unattended, and do not start the 9.x upgrade until every node is on current 8.4 packages. If you run hyper-converged Ceph, use this 8.4 window to get Ceph Squid ready before the major Proxmox VE 9 upgrade.
pvesh get /cluster/resources --type node
pveversion | grep pve-manager
ceph -s 2>/dev/null || true
ceph --version 2>/dev/null || true
When To Continue To 9.x
Continue only after the whole environment is stable on 8.4, backups have been tested, and you have console access in case a network interface name changes during the Debian 13 jump. The next guide in this set is the Proxmox VE 8.4 to 9.1 walkthrough.
Related Catch-Up Guides
- Proxmox VE 8.4 to 9.1 upgrade guide
- Proxmox Backup Server 3.4 to 4.2 upgrade guide
- Proxmox Mail Gateway 8.2 to 9.0 upgrade guide