public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs] bootloaders: add secure boot shim example
Date: Thu, 2 Jul 2026 11:11:07 +0200	[thread overview]
Message-ID: <20260702111107.78156f30@rosa.proxmox.com> (raw)
In-Reply-To: <20260702085758.48099-1-m.sandoval@proxmox.com>

Thanks for addressing this so quickly!

On Thu,  2 Jul 2026 10:57:41 +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) [..]
> 
>  system-booting.adoc | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/system-booting.adoc b/system-booting.adoc
> index da87697..c3de158 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 output contains a line that looks similar to the following, GRUB is
> +used in UEFI mode with Secure Boot enabled.
I'd rather phrase that as:
If the active boot entry points to `\EFI\proxmox\shimx64.efi`, then secure
boot is enabled. 
(It's not set in stone that grub is the only boot-loader that can be
loaded from a signed shim - at some point in the future we might have
systemd-boot in that list as well, and prefer that for new installs)

alternatively we will need to rework the docs then anyways - so it's just
a suggestion - what do you think?

> +
> +----
> +Boot0005* proxmox	[...] File(\EFI\proxmox\shimx64.efi)
> +----
> +
>  If the output contains a line similar to the following, `systemd-boot` is used.
>  
>  ----





  reply	other threads:[~2026-07-02  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  8:57 [PATCH docs] bootloaders: add secure boot shim example Maximiliano Sandoval
2026-07-02  9:11 ` Stoiko Ivanov [this message]
2026-07-02  9:14   ` Maximiliano Sandoval
2026-07-02  9:16     ` Stoiko Ivanov
2026-07-02  9:36       ` superseded: " Maximiliano Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260702111107.78156f30@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=m.sandoval@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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