From: Andy Smith <andy@strugglers.net>
To: Jeremi Piotrowski <jeremi.piotrowski@gmail.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Pry Mar <pryorm09@gmail.com>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [Xen-devel] bug: unable to LZ4 decompress ub1910 installer kernel when launching domU
Date: Mon, 2 Dec 2019 14:28:22 +0000 [thread overview]
Message-ID: <20191202142822.GY32576@bitfolk.com> (raw)
In-Reply-To: <20191201174714.GA13968@gentoo-tp.home>
Hello,
On Sun, Dec 01, 2019 at 06:47:14PM +0100, Jeremi Piotrowski wrote:
> On Thu, Oct 24, 2019 at 10:12:19AM +0200, Jan Beulich wrote:
> > Would you please increase verbosity (xl -vvv create ...) such that we
> > can see what exactly the decompression code doesn't like about this
[…]
> I stumbled across the same issue
In case it is useful, I was recently chatting to Pry Mar on IRC
about this issue. It also affects the Ubuntu 20.04 kernels (both
installer and OS packaged) which is no surprise since it seems they
switched to LZ4 compression from 19.10.
Pry Mar was able to make it boot under Xen PV by manually
uncompressing the vmlinuz first.
I have been meaning to take a recent Debian kernel or mainline
kernel and enable the LZ4 compression options to see if it is
reproducible outside of Ubuntu, but haven't found time yet.
Thanks,
Andy
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-02 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:33 [Xen-devel] bug: unable to LZ4 decompress ub1910 installer kernel when launching domU Pry Mar
2019-10-24 8:12 ` Jan Beulich
2019-12-01 17:47 ` Jeremi Piotrowski
2019-12-02 14:28 ` Andy Smith [this message]
2019-12-03 8:02 ` Jan Beulich
2019-12-04 7:14 ` Jeremi Piotrowski
2019-12-04 13:10 ` Jan Beulich
2019-12-04 13:27 ` Jan Beulich
2019-12-05 1:20 ` Pry Mar
2019-12-06 6:25 ` Jeremi Piotrowski
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=20191202142822.GY32576@bitfolk.com \
--to=andy@strugglers.net \
--cc=jbeulich@suse.com \
--cc=jeremi.piotrowski@gmail.com \
--cc=pryorm09@gmail.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).