From: Andy Smith <andy@strugglers.net>
To: Juergen Gross <jgross@suse.com>
Cc: grub-devel@gnu.org
Subject: Re: grub PVHv2 booting patch series - no block devices available in guest
Date: Tue, 23 Jan 2018 07:44:02 +0000 [thread overview]
Message-ID: <20180123074402.GX29360@bitfolk.com> (raw)
In-Reply-To: <bd76b1b6-0d55-5e7f-e715-46a5d4458e9e@suse.com>
Hi Juergen,
Thanks for replying so quickly!
On Tue, Jan 23, 2018 at 08:28:19AM +0100, Juergen Gross wrote:
> On 23/01/18 08:18, Andy Smith wrote:
> > The selected kernel and initramfs are read and it does boot that
> > but there do not appear to be any block devices so it ultimately
> > fails to find root filesystem.
>
> You will need some more Linux kernel patches:
>
> https://lists.xen.org/archives/html/xen-devel/2017-11/msg01681.html
Ah, that is a shame. I was investigating this now because I thought
with PVHv2 support available since 4.11 there was a good chance that
a modern guest distribution release (in this specific case
"debtest1" was in fact Ubuntu 16.04 LTS with HWE 4.13 kernel) would
be usable without additional guest modifications.
I see now that at the moment this really only means usable by
directly supplying kernel and initramfs, which is not going to work
for my users who like to choose between several distributions and
control their own kernels.
I will evaluate again when/if these patches become available in
distribution packaged kernels.
Thanks,
Andy
prev parent reply other threads:[~2018-01-23 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 7:18 grub PVHv2 booting patch series - no block devices available in guest Andy Smith
2018-01-23 7:28 ` Juergen Gross
2018-01-23 7:44 ` Andy Smith [this message]
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=20180123074402.GX29360@bitfolk.com \
--to=andy@strugglers.net \
--cc=grub-devel@gnu.org \
--cc=jgross@suse.com \
/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.