From: Andy Smith <andy@strugglers.net>
To: grub-devel@gnu.org
Subject: Confusion regarding LZ4-compressed kernel support and Xen (PV)
Date: Sat, 25 Apr 2020 23:38:51 +0000 [thread overview]
Message-ID: <20200425233851.GD3767@bitfolk.com> (raw)
Hi,
I am booting Xen PV guests using a grub image compiled as a PV guest
and then having that parse the /boot/grub/grub.cfg from within the
guest.
When this encounters an LZ4-compressed kernel I get this:
Loading Linux 5.4.0-26-generic ...
error: not xen image. [ vmlinuz-5.4.0-26-gen 10B 0% 0.00B/s ]
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue...
I know it is a problem related to LZ4 compression because if I
manually decompress that kernel image then I am able to boot it
fine.
Cloning https://git.savannah.gnu.org/git/grub.git just now and
rebuilding my PV grub image gives the same result.
I see the error message comes from:
grub-core/loader/i386/xen_file.c
92: grub_error (GRUB_ERR_BAD_OS, "not xen image");
I cannot see any evidence that there is LZ4 support in that file,
but I don't really know what I'm looking for so quite possibly I am
wrong.
Searching the web finds articles about Ubuntu's decision to switch
to LZ4-compressed kernels and some of these mention that this
required changes to grub. I was also unable to find any actual
details of the patch/commit for that. Again, if it's present at:
https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu
…then it's not obvious to me.
Does upstream grub have support for booting LZ4-compressed kernels?
Is that also expected to work when grub is booted as a Xen PV image?
I am just a bit lost as to where to look to find a solution to this,
so any pointers would be much appreciated.
Thanks,
Andy
next reply other threads:[~2020-04-25 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 23:38 Andy Smith [this message]
2020-04-26 1:24 ` Confusion regarding LZ4-compressed kernel support and Xen (PV) Andy Smith
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=20200425233851.GD3767@bitfolk.com \
--to=andy@strugglers.net \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.