https://blog.margrop.net/en/tag/proxmox-ve-9/ Recent content in Proxmox VE 9 on Margrop Blog Hugo -- gohugo.io en-US Tue, 12 May 2026 19:00:00 +0800 https://blog.margrop.net/en/post/pve8-to-pve9-agent-manual-upgrade-guide/ Tue, 12 May 2026 19:00:00 +0800 https://blog.margrop.net/en/post/pve8-to-pve9-agent-manual-upgrade-guide/ <blockquote> <p><strong>Short version</strong></p> <p>Upgrading Proxmox VE 8 to 9 is not just copying a few commands. It is a major system upgrade from Debian Bookworm to Trixie, from PVE 8.4 to PVE 9.x, with kernel, storage, networking, Ceph, and HA behavior in the blast radius. The fastest practical path is to let Codex, Claude, OpenClaw, HermesAgent, or a similar Agent handle checks, command sequencing, logging, and post-upgrade verification. The human operator still needs to approve repository changes, package removals, configuration prompts, reboot timing, and recovery decisions. If you prefer doing everything by hand, the second half of this article gives a concrete manual checklist.</p> </blockquote> <p>This article is for two groups of operators. The first group already uses Agents over SSH and wants a scoped one-sentence task for upgrading PVE. The second group prefers typing every command manually and wants a clear, ordered procedure with the main risk points called out.</p> <p>All hostnames, addresses, repositories, tokens, and accounts in this article are placeholders. Replace values such as <code>&lt;PVE_NODE&gt;</code>, <code>&lt;BACKUP_TARGET&gt;</code>, and <code>&lt;ADMIN_CONSOLE&gt;</code> with your own environment. Before touching a production host, read the official Proxmox documentation and verify that your backups are restorable.</p>