From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 0D7B51FF135 for ; Thu, 02 Jul 2026 11:32:20 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 4E7A7213BD; Thu, 02 Jul 2026 11:32:19 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 1/1] bootloaders: add secure boot shim example Date: Thu, 2 Jul 2026 11:31:58 +0200 Message-ID: <20260702093215.84124-1-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1782984729357 X-SPAM-LEVEL: Spam detection results: 0 DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: VGM7W5FTXG3Y5OZ6R63EQMXARQGV43RW X-Message-ID-Hash: VGM7W5FTXG3Y5OZ6R63EQMXARQGV43RW X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On a system that was migrated from systemd-boot to grub2 with secure boot, the entry grubx64.efi would be missing and the systemd-bootx64.efi entry would be present. If the shimx64.efi entry is not mentioned, then the docs would incorrectly imply that the system uses systemd-boot as a bootloader. We add the shimx64.efi entry to the docs to fill this gap. Suggested-by: Stoiko Ivanov Signed-off-by: Maximiliano Sandoval --- Notes: On my machine: $ efibootmgr -v Boot0000* Linux Boot Manager HD(2,GPT,[..])/File(\EFI\systemd\systemd-bootx64.efi) [..] [..] Boot0002* proxmox HD(2,GPT,[..])/File(\EFI\proxmox\shimx64.efi) [..] Differences from v1: - Explicitly say that we use secure boot only if the boot is, indeed, the active one system-booting.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/system-booting.adoc b/system-booting.adoc index da87697..9fb7ef1 100644 --- a/system-booting.adoc +++ b/system-booting.adoc @@ -209,6 +209,13 @@ used in UEFI mode. Boot0005* proxmox [...] File(\EFI\proxmox\grubx64.efi) ---- +If the active boot entry points to `\EFI\proxmox\shimx64.efi` like in the +following example, GRUB is used in UEFI mode with Secure Boot enabled. + +---- +Boot0005* proxmox [...] File(\EFI\proxmox\shimx64.efi) +---- + If the output contains a line similar to the following, `systemd-boot` is used. ---- -- 2.47.3