Proxmox 8.0 于 2023 年 6 月 22 日发布，包含令人兴奋的新功能。 亮点包括直接来自 Proxmox 官方论坛的以下内容：
- Debian 12，但使用较新的 Linux 内核6.2
- QEMU 8.0.2、LXC 5.0.2、ZFS 2.1.12
- Ceph Quincy 17.2 是默认版本，并将继续受到支持。
- Ceph 现在拥有一个可通过任何 Proxmox VE 订阅访问的企业存储库，为生产系统提供最佳稳定性。
- 安装程序 ISO 的附加基于文本的用户界面 (TUI)。
- 配置虚拟来宾时，将主机网桥和 VNet 访问集成到 Proxmox VE 的 ACL 系统中。
- 添加访问领域同步作业，以方便、自动地定期从 LDAP/AD 服务器同步用户和组。
- VM 的新默认 CPU 类型：x86-64-v2-AES
- 资源分配：PCI(e) 或 USB 设备与 Proxmox VE 集群中的节点之间。
- 无数的 GUI 和 API 改进。
虽然您可以轻松备份现有虚拟机，然后使用新版本的 Proxmox 重新安装服务器，但我将向您展示如何从版本 7.4 就地升级到版本 8.0。
1.) 首先，您应该确保备份所有现有的虚拟机和容器，以防升级过程中出现问题。 然后，您需要关闭它们，或者，如果您有一个集群并且需要保持高可用性，请将它们从要升级的节点迁移。 查看我有关备份虚拟机和创建节点集群的教程，以了解有关这些操作的更多信息。 您还需要根安装点上至少有 5GB 的磁盘空间以及对节点的 SSH 或控制台访问。 （这样比较安全）
root@upgrade:~# qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID
100 backuptest stopped 2048 32.00 0 2.) 确保系统使用 APT 来使用最新的 Proxmox VE 7.4 软件包。
apt update
apt dist-upgrade
pveversion最后一个命令应至少返回 v7.4.15。
笔记：如果您没有订阅付费企业支持，您可能需要禁用企业存储库并启用测试存储库。 为此，请单击您的节点，然后单击“更新”下的“存储库”并取消选中 Enterprise 存储库。 然后您可以添加“测试”存储库。
3.) 最新的 Proxmox 7.4 软件包附带了一个名为 pve7to8 的工具。 您应该在要更新的节点上的终端会话中运行此命令：
pve7to8 --full该脚本会检查并报告在即将进行的升级过程中发现的任何潜在问题，但不会修复它。 如果有任何问题需要修复，您应该在修复问题的同时再次运行脚本，以确保问题确实得到解决。 请注意，如果您尚未从要升级的节点迁移任何虚拟机，则脚本可能会警告您这些虚拟机存在。 但是，如果您不需要 HA，则可以忽略这一点。
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
PASS: all packages up-to-date
Checking proxmox-ve package version..
PASS: proxmox-ve package has version >= 7.4-1
Checking running kernel version..
PASS: running kernel '5.15.102-1-pve' is considered suitable for upgrade.
= CHECKING CLUSTER HEALTH/SETTINGS =
SKIP: standalone node.
= CHECKING HYPER-CONVERGED CEPH STATUS =
SKIP: no hyper-converged ceph setup detected!
= CHECKING CONFIGURED STORAGES =
PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage re-uses a directory for multiple content types.
= MISCELLANEOUS CHECKS =
INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvescheduler.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for supported & active NTP service..
PASS: Detected active time synchronisation unit 'chrony.service'
INFO: Checking for running guests..
PASS: no running guest detected.
INFO: Checking if the local node's hostname 'upgrade' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '192.168.122.230' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs for clashes with new 'PVE' namespace..
PASS: no custom roles defined, so no clash with 'PVE' role ID namespace enforced in Proxmox VE 8
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
SKIP: not yet upgraded, no need to check the FUSE library version LXCFS uses
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking if the suite for the Debian security repository is correct..
PASS: found no suite mismatch
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
SKIP: not yet upgraded, no need to check the presence of systemd-boot
SKIP: No containers on node detected.
= SUMMARY =
TOTAL: 29
PASSED: 24
SKIPPED: 5
WARNINGS: 0
FAILURES: 0
root@upgrade:/# 4.) 更新一切 Debian 以及书虫上的 Proxmox VE 存储库条目：
sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list5.) 更新存储库包索引：
sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list6.) 更新系统 Debian 书虫和 Proxmox VE 8.0：
apt dist-upgrade执行该命令所需的时间取决于服务器的处理能力。 如果您的 Proxmox 安装基于快速 SSD 驱动器，它将比机械驱动器更快。 作为该过程的一部分，您将被要求批准对配置文件的各种更改。 以下是 Proxmox 官方升级文档中推荐的选项：
/etc/issue -> Proxmox VE will auto-generate this file on boot, and it has only cosmetic effects on the login console.
Using the default "No" (keep your currently-installed version) is safe here.
/etc/lvm/lvm.conf -> Changes relevant for Proxmox VE will be updated, and a newer config version might be useful.
If you did not make extra changes yourself and are unsure it's suggested to choose "Yes" (install the package maintainer's version) here.
/etc/ssh/sshd_config -> If you have not changed this file manually, the only differences should be a replacement of ChallengeResponseAuthentication no with KbdInteractiveAuthentication no and some irrelevant changes in comments (lines starting with #).
If this is the case, both options are safe, though we would recommend installing the package maintainer's version in order to move away from the deprecated ChallengeResponseAuthentication option. If there are other changes, we suggest to inspect them closely and decide accordingly.
/etc/default/grub -> Here you may want to take special care, as this is normally only asked for if you changed it manually, e.g., for adding some kernel command line option.
It's recommended to check the difference for any relevant change, note that changes in comments (lines starting with #) are not relevant.
If unsure, we suggested to selected "No" (keep your currently-installed version)7.) 脚本成功完成后，再次运行 pve7to8 检查器脚本：
pve7to8 --full8.) 如果没有问题，请重新启动。 如果成功，您将进入新的 Proxmox 安装。 您现在可以重新启动虚拟机。 你完成了！
