From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Roman Shaposhnik <roman@zededa.com>,
Xen-devel <xen-devel@lists.xenproject.org>, <grub-devel@gnu.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: multiboot2 and module2 boot issues via GRUB2
Date: Thu, 1 Apr 2021 10:44:35 +0200 [thread overview]
Message-ID: <YGWH89ubVe104Tnl@Air-de-Roger> (raw)
In-Reply-To: <b5ed3a53-5152-aba1-820d-ccab72a82c61@suse.com>
On Thu, Apr 01, 2021 at 09:31:07AM +0200, Jan Beulich wrote:
> On 01.04.2021 03:06, Roman Shaposhnik wrote:
> > And the obvious next question: is my EVE usecase esoteric enough that
> > I should just go ahead and do a custom GRUB patch or is there a more
> > general interest in this?
>
> Not sure if it ought to be a grub patch - the issue could as well
> be dealt with in Xen, by concatenating modules to form a monolithic
> initrd.
I would rather have it done in the loader than Xen, mostly because
it's a Linux boot specific format, and hence I don't think Xen should
have any knowledge about it.
If it turns out to be impossible to implement on the loader side we
should consider doing it in Xen, but that's not my first option.
Thanks, Roger.
next prev parent reply other threads:[~2021-04-01 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 18:28 multiboot2 and module2 boot issues via GRUB2 Roman Shaposhnik
2021-03-30 19:08 ` Andrew Cooper
2021-04-01 1:06 ` Roman Shaposhnik
2021-04-01 7:31 ` Jan Beulich
2021-04-01 8:44 ` Roger Pau Monné [this message]
2021-04-01 19:43 ` Andrew Cooper
2021-04-06 8:19 ` Jan Beulich
2021-04-06 17:37 ` Roman Shaposhnik
2021-04-06 17:51 ` Andrew Cooper
2021-04-06 18:03 ` Roman Shaposhnik
2021-04-06 18:41 ` Andrew Cooper
2021-04-07 20:50 ` Glenn Washburn
2021-04-08 16:48 ` Daniel Kiper
2021-03-30 19:35 ` Elliott Mitchell
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=YGWH89ubVe104Tnl@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=grub-devel@gnu.org \
--cc=jbeulich@suse.com \
--cc=roman@zededa.com \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).