From: Pry Mar <pryorm09@gmail.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: [Xen-devel] bug: unable to LZ4 decompress ub1910 installer kernel when launching domU
Date: Wed, 23 Oct 2019 13:33:12 -0700 [thread overview]
Message-ID: <CAHnBbQ8Xt=f_P+sntM27m7+NXft-U=DYXFdTV9hOqJBTU+CXNw@mail.gmail.com> (raw)
Hello xen-devel,
https://paste.debian.net/plain/1109374
shows my traces from a healthy CentOS 8, xen-4.12.1 dom0 when trying
to launch a pv install of the newly released ub1910. The source is a
block-attached ISO and the kernel/ramdisk was copied off locally.
Iso is named, eoan-live-server-amd64.iso.
There is also a kernel pair here
http://archive.ubuntu.com/ubuntu/dists/eoan/main/installer-amd64/current/images/netboot/xen/
which behaves the same.
The `LZ4 decompress error` happened with other dom0, including
xen-4.13~rc1 on Buster.
ub1910 dom0 test
----
My goal with this domU install was to prepare a golden image for Eoan
dom0. I had trouble testing a fresh ub1910 build of xen-4.12.1 on a
good bare-metal install. The only doubt I had was the
`do-release-upgrade -d` from ub1904.
My new hypervisor would not even start in ub1910 and I got an install boot-loop.
cheers,
PryMar56
##xen-packaging on Freenode
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-10-23 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:33 Pry Mar [this message]
2019-10-24 8:12 ` [Xen-devel] bug: unable to LZ4 decompress ub1910 installer kernel when launching domU Jan Beulich
2019-12-01 17:47 ` Jeremi Piotrowski
2019-12-02 14:28 ` Andy Smith
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='CAHnBbQ8Xt=f_P+sntM27m7+NXft-U=DYXFdTV9hOqJBTU+CXNw@mail.gmail.com' \
--to=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).