public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* [PATCH docs v2 1/1] bootloaders: add secure boot shim example
@ 2026-07-02  9:31 Maximiliano Sandoval
  2026-07-02  9:34 ` Stoiko Ivanov
  2026-07-02 13:55 ` applied: " Thomas Lamprecht
  0 siblings, 2 replies; 3+ messages in thread
From: Maximiliano Sandoval @ 2026-07-02  9:31 UTC (permalink / raw)
  To: pve-devel

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 <s.ivanov@proxmox.com>
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---

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





^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH docs v2 1/1] bootloaders: add secure boot shim example
  2026-07-02  9:31 [PATCH docs v2 1/1] bootloaders: add secure boot shim example Maximiliano Sandoval
@ 2026-07-02  9:34 ` Stoiko Ivanov
  2026-07-02 13:55 ` applied: " Thomas Lamprecht
  1 sibling, 0 replies; 3+ messages in thread
From: Stoiko Ivanov @ 2026-07-02  9:34 UTC (permalink / raw)
  To: Maximiliano Sandoval; +Cc: pve-devel

Thanks for the quick iteration!

change LGTM - and we'll rework it if/when secure-boot with something !=
grub is an option.

Reviewed-by: Stoiko Ivanov <s.ivanov@proxmox.com> 

On Thu,  2 Jul 2026 11:31:58 +0200
Maximiliano Sandoval <m.sandoval@proxmox.com> wrote:

> 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 <s.ivanov@proxmox.com>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> 
> 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.
>  
>  ----





^ permalink raw reply	[flat|nested] 3+ messages in thread

* applied: [PATCH docs v2 1/1] bootloaders: add secure boot shim example
  2026-07-02  9:31 [PATCH docs v2 1/1] bootloaders: add secure boot shim example Maximiliano Sandoval
  2026-07-02  9:34 ` Stoiko Ivanov
@ 2026-07-02 13:55 ` Thomas Lamprecht
  1 sibling, 0 replies; 3+ messages in thread
From: Thomas Lamprecht @ 2026-07-02 13:55 UTC (permalink / raw)
  To: pve-devel, Maximiliano Sandoval

On Thu, 02 Jul 2026 11:31:58 +0200, Maximiliano Sandoval wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/1] bootloaders: add secure boot shim example
      commit: d4093b7ffb78385ae6f5e125e99bbf31c131e3a0




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-07-02 13:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-02  9:31 [PATCH docs v2 1/1] bootloaders: add secure boot shim example Maximiliano Sandoval
2026-07-02  9:34 ` Stoiko Ivanov
2026-07-02 13:55 ` applied: " Thomas Lamprecht

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal