From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC pve-kernel-meta 0/5] unify boot-mode config
Date: Wed, 2 Feb 2022 15:28:55 +0100 [thread overview]
Message-ID: <20220202152855.040d20c1@rosa.proxmox.com> (raw)
In-Reply-To: <897a7e1f-929f-24cc-41af-dcbf1158102c@proxmox.com>
On Wed, 2 Feb 2022 10:03:05 +0100
Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:
> On 01.02.22 23:03, Stoiko Ivanov wrote:
> > patch 3 drops systemd-boot and uses grub for both boot-modes, hopefully
> > unifying the boot-experience and causing less confusion (currently I suggest
> > to look at the screen while booting to find out which boot-loader is used)
> >
> > (Sadly systemd-boot (which I would prefer, justifiably)
> > won't get support for legacy boot)
> >
> The thing is, non-uefi systems will become more rare anyhow, so why
> bother with that? The simplicity of systemd-boot is worth the few (?)
> confusion - I mean what exactly is there confusing anyway, if most relevant
> actions can be handled through our tool anyway?
>
> I'm not definitive yet, but currently rather tending to NACK that.
Thanks for the feedback!
Hmm - I do see your point - motivation was that it felt like a logical
next step after adapting the config of systemd-boot to get the images
from where grub needs them to have the system bootable in both modes -
and having a single place to configure the boot-loader (kernel cmdline,
pinning) seemed sensible (and less code in p-b-t should correlate with
less bugs in p-b-t).
Add to that my biased view (a few forum-threads where people did not know
which boot loader they used - e.g. [0,1,2] vs. the silent majority, who
either does not need it, or knows it) that most users expect
/etc/default/grub to be the place for editing the kernel commandline
(following the blog/forum/website posts only mentioning this)
But OTOH I was a bit hesitant as well (since it would mean that the
blog/forum/website posts of the past 2 years would now become 'wrong' and
cause even more confusion). Also (quite biased as well) - there are quite
a few threads with grub failing to boot vs. none that I'm aware of, where
systemd-boot fails.
So - no hard feelings from my side either - I was curios if it would work
as a POC
On a side-note - I just learned that grub in efi-mode works fine (without
explicit configuration) over a serial terminal (a use-case I need for
myself ;)
[0]
https://forum.proxmox.com/threads/amd-core-display-pass-through-install-win10-does-not-start.103651/post-447007
[1]
https://forum.proxmox.com/threads/unable-to-boot-after-pve-efiboot-tool-refresh.103149/
[2]
https://forum.proxmox.com/threads/no-iommu-detected-please-activate-it.102119/
next prev parent reply other threads:[~2022-02-02 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 22:03 Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 1/5] rename pve-efiboot-manual-kernels to proxmox-boot-manual-kernels Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 2/5] proxmox-boot: add reinit subcommand Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 3/5] proxmox-boot: keep EFI and legacy bootloaders in sync Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 4/5] proxmox-boot: use grub for UEFI boot Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 5/5] proxmox-boot: install grub in esp/EFI/BOOT/BOOTX64.EFI Stoiko Ivanov
2022-02-02 9:03 ` [pve-devel] [RFC pve-kernel-meta 0/5] unify boot-mode config Thomas Lamprecht
2022-02-02 14:28 ` Stoiko Ivanov [this message]
2022-02-02 14:42 ` Thomas Lamprecht
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=20220202152855.040d20c1@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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