From: Elliott Mitchell <ehem+xen@m5p.com>
To: Roman Shaposhnik <roman@zededa.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: multiboot2 and module2 boot issues via GRUB2
Date: Tue, 30 Mar 2021 12:35:28 -0700 [thread overview]
Message-ID: <YGN9gL0yl8IWSkDI@mattapan.m5p.com> (raw)
In-Reply-To: <CAMmSBy8Wpwgj3V0U8OhsZCgyAxOjTeHDMt-Vw+om1koopmxTsg@mail.gmail.com>
On Tue, Mar 30, 2021 at 11:28:49AM -0700, Roman Shaposhnik wrote:
> seems like I've run into an issue with multiboot2 and module2
> commands that I can't quite explain. Since it may be something
> super simply and silly -- I wanted to reach out here before I do
> a GRUB/Xen/LK source deepdive.
>
> So here's the deal: whenever I boot straight up Linux kernel
> I can do the following sequence of commands:
> linux /kernel
> initrd foo.cpio.gz bar.cpio.gz
> and have linux kernel effectively stack content of bar.cpio.gz
> on top of foo.cpio.gz and present a unified initramfs that way.
>
> I'm trying to replicate it with Xen, but:
> multiboot2 /boot/xen.gz
> module2 /kernel
> module2 foo.cpio.gz
> module2 bar.cpio.gz
> only seems to be picking up foo.cpio.gz
>
> Has anyone run into this issue before?
Not I, but I asked questions elsewhere before I fought this battle. You
should get a more recent version of GRUB.
More recent versions of GRUB (2.04) on ARM have the "xen_hypervisor" boot
mode. With this boot mode the kernel and initrd get passed via
xen_module command.
Apparently newer GRUB versions have better boot methods for Xen, so
updating would be a Good Idea, if that is viable for you.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
prev parent reply other threads:[~2021-03-30 19:36 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é
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 [this message]
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=YGN9gL0yl8IWSkDI@mattapan.m5p.com \
--to=ehem+xen@m5p.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).