Post-Upgrade Tasks

After the host reboots into Proxmox VE 9.x, complete the following before returning it to service.

Verify the upgrade

Confirm the host now reports a 9.x version:

pveversion

Re-run the checklist and confirm there are no remaining problems:

pve8to9

In the Proxmox web UI, empty your browser cache / force-reload (CTRL + SHIFT + R, or ⌘ + Option + R on macOS) so the updated interface loads correctly.

Re-run the NDG PVE Post Install Script

The NDG PVE Post Install Script (v0.9 or later) detects Proxmox VE 9 and reapplies the correct repositories and NDG configuration (custom CPU models, datacenter tags, and so on).

From the host shell, run:

bash -c "$(curl -fsSL https://ndg.tech/pve-post-install)"

See the NDG PVE Post Install Script page for details on what it does.

Verify network interface names

Warning

The Proxmox VE 9 kernel can rename network interfaces on some hardware (for example, ens4f0np0 could change). Because NETLAB+ networking depends on specific interface names, verify them before bringing the host back into service.

Confirm that the interfaces referenced in /etc/network/interfaces — your management bridge (vmbr0), CLUSTER_NET, and NLCONTROL — still match the physical NICs.

Tip

If interface names changed, Proxmox VE 9 provides the pve-network-interface-pinning tool to pin stable names. Update /etc/network/interfaces accordingly and reapply the network configuration.

Verify NETLAB+ connectivity

  • In NETLAB+, confirm the Proxmox datacenter/host reconnects and reports healthy.

  • Confirm SSH between the NETLAB+ VM and the host is working — NETLAB+ manages host networking over SSH.

  • Start a test pod to confirm cloning and networking behave normally.

Clusters

Repeat the entire procedure on the next node, starting from Prerequisites & Preparation. Upgrade and verify one node at a time until all nodes report Proxmox VE 9.x.

NETLAB+-specific notes

Proxmox VE 9 changes and how they affect NETLAB+

Topic

Note

Network interface naming

The most impactful item for NETLAB+ — verify after every node upgrade (see above).

High Availability (HA)

The NDG Post Install Script disables HA, so the PVE 9 HA-groups-to-HA-rules change does not apply.

Containers (cgroup v1)

Proxmox VE 9 removes legacy cgroup v1. NETLAB+ uses virtual machines, not LXC containers, so this does not apply.

LVM autoactivation

On PVE 9, new logical volumes default to autoactivation disabled. The pve8to9 checklist flags any action needed.

High memory reported

Proxmox may report high VM memory usage due to ballooning/accounting; this is normal. See the Release Notes.