xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Roman Shaposhnik <roman@zededa.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Subject: multiboot2 and module2 boot issues via GRUB2
Date: Tue, 30 Mar 2021 11:28:49 -0700	[thread overview]
Message-ID: <CAMmSBy8Wpwgj3V0U8OhsZCgyAxOjTeHDMt-Vw+om1koopmxTsg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

Hi!

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?

Thanks,
Roman.

[-- Attachment #2: Type: text/html, Size: 1095 bytes --]

             reply	other threads:[~2021-03-30 18:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 18:28 Roman Shaposhnik [this message]
2021-03-30 19:08 ` multiboot2 and module2 boot issues via GRUB2 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

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=CAMmSBy8Wpwgj3V0U8OhsZCgyAxOjTeHDMt-Vw+om1koopmxTsg@mail.gmail.com \
    --to=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).