docs(pve9 plan): headers must be present before the upgrade (nh3-pve lesson)

2026-10-03 14:09:47 -07:00
parent d9e09fed14
commit 5e25d4bae1
1 changed files with 4 additions and 1 deletions
@@ -54,7 +54,10 @@ Quorum: 2 nodes × 1 vote, no QDevice, no `two_node`.
   change predictable names, and a renamed uplink leaves `vmbr0` with no link: the whole node is off the
   network. pve8to9 did not flag it; this is a precaution. Template: `playbooks/nh3-pve-pin-nic-names.yaml`.
   Uplinks today: `pve` `enp3s0f0np0` (X710), `esh-nas-pve` `enp5s0f0`.
-5. **NVIDIA on `pve`:** 580.178.04 is DKMS-built for 6.8. After the dist-upgrade and **before**
+5. **NVIDIA on `pve`:** first make sure `proxmox-default-headers` is installed. On nh3-pve (2026-10-03) the upgrade put
+   in kernel 7.0 with NO 7.0 headers, so DKMS never built the module and the GPU container did not start. The fix was
+   `apt install proxmox-default-headers proxmox-headers-<new>` + `dkms autoinstall`. 580.178.04 does compile on 7.0.14.
+   (`playbooks/nh3-pve-pve9-postfix.yaml`.) 580.178.04 is DKMS-built for 6.8. After the dist-upgrade and **before**
   rebooting, `dkms status` must show the module built for the new kernel; if not, reinstall the
   driver for trixie before rebooting. esh-ml1 (CT 110) is the fleet's **only** embed/rerank backend
   behind LiteLLM, and albok-service now depends on it. **Put nh3-ml1 (its twin) behind the gateway