All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: "Jürgen Groß" <jgross@suse.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	xen-users <xen-users@lists.xenproject.org>
Subject: Re: Grub xen_pvh platform does not seem to support uncompressed kernels
Date: Mon, 2 Nov 2020 08:27:23 +0000	[thread overview]
Message-ID: <20201102082723.GO16003@bitfolk.com> (raw)
In-Reply-To: <5b764199-29de-70ef-ea68-971737caaa70@suse.com>

Hi Jürgen,

On Mon, Nov 02, 2020 at 08:43:24AM +0100, Jürgen Groß wrote:
> On 02.11.20 07:22, Andy Smith wrote:
> >I therefore can only conclude that PVH grub doesn't like kernels
> >with no compression. Is that expected?
> 
> Can you boot the decompressed kernel on bare metal or in an HVM
> domain using grub?

Oh that's interesting. The decompressed kernel doesn't boot bare
metal either (same message).

The decompressed kernel is generated like this:

# extract-vmlinux /boot/vmlinuz-5.4.0-52-generic > /boot/vmlinuz-5.4.0-52-generic-decompressed

The decompressed kernel does boot when presented to the hypervisor
directly, i.e. no grub, directly listed in guest config file.

I don't have an HVM test setup right now so am unable to test that,
but I suppose we can assume it will fail as the problem is in the
standard grub loading functions.

So, is this a bug? Grub should be able to boot uncompressed kernels,
shouldn't it?

Thanks,
Andy


  reply	other threads:[~2020-11-02  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  6:22 Grub xen_pvh platform does not seem to support uncompressed kernels Andy Smith
2020-11-02  7:43 ` Jürgen Groß
2020-11-02  8:27   ` Andy Smith [this message]
2020-11-02  8:43     ` Jürgen Groß
2020-11-02  9:17       ` Andy Smith
2020-11-02  9:39         ` Jürgen Groß

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=20201102082723.GO16003@bitfolk.com \
    --to=andy@strugglers.net \
    --cc=grub-devel@gnu.org \
    --cc=jgross@suse.com \
    --cc=xen-users@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 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.