From f2c6b3f112bac0b976cb3780c91b343b17db3fec Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Wed, 24 Jun 2026 00:34:05 -0400 Subject: [PATCH] Resolve VM 101 EFI certificate warning --- docs/proxmox-ve-8-to-9-upgrade-plan.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/proxmox-ve-8-to-9-upgrade-plan.md b/docs/proxmox-ve-8-to-9-upgrade-plan.md index 64ca2338..2447b4f5 100644 --- a/docs/proxmox-ve-8-to-9-upgrade-plan.md +++ b/docs/proxmox-ve-8-to-9-upgrade-plan.md @@ -51,15 +51,15 @@ Completed on 2026-06-23. previous VM CPU model. - Disabled the generated PVE enterprise deb822 source with `Enabled: no` so no-subscription APT updates remain clean. +- On 2026-06-24, enrolled the updated Microsoft UEFI 2023 certificates for the + camera/NVR VM EFI disk with `qm enroll-efi-keys`, then started the VM with no + EFI certificate warning and verified Frigate Docker health `healthy`. ## Residual Follow-Ups - Full retained VM backup archives were not found during inventory. Host config backups were captured, but this should be improved with a real enabled VM backup target and restore test. -- One OVMF VM emitted a UEFI certificate warning on start. Plan a shutdown - window to enroll updated EFI keys with the Proxmox UI action or - `qm enroll-efi-keys` after checking guest OS implications. - `pve8to9` reported old-format RRD files as informational post-upgrade data. Keep them if historical graphs are useful; delete only if old history is not needed.