From: M A Young <m.a.young@durham.ac.uk>
To: Steven Haigh <netwiz@crc.id.au>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] /sys/hypervisor entries for Xen (Domain-0, PV, PVH and HVM)
Date: Wed, 9 Oct 2019 09:00:16 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.1910090855001.4406@algedi.dur.ac.uk> (raw)
In-Reply-To: <1570594496.2508.0@crc.id.au>
On Wed, 9 Oct 2019, Steven Haigh wrote:
> Hi all,
>
> I'm working on fixing up the grub packages for Fedora in deducing the new BLS
> logic in Fedora and disabling it in non-compatible environments.
>
> BZ Report:
> https://bugzilla.redhat.com/show_bug.cgi?id=1703700
>
> Currently, it seems that we can deduce the following two scenarios:
>
> in /sys/hypervisor:
>
> 1) type == xen && uuid == all zeros, then this is BLS safe (the Domain-0).
> 2) type == xen && uuid != all zeros, then this is BLS *unsafe* (covers PV, HVM
> and PVH guests).
>
> Is there any other variables that come into effect that could cause a
> variation in the above checks as to enable or disable BLS?
>
> Right now, I'm proposing that we try to disable the new BLS behaviour in
> Fedora for PV, HVM and PVH guests - as pygrub is not up to the task of booting
> them. We included HVM as it may be common for users to switch between HVM and
> PVH configurations for the same installed VM.
I do have a long term plan to try to get pygrub to handle BLS, though I
don't expect to have it working soon.
Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-09 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 4:14 [Xen-devel] /sys/hypervisor entries for Xen (Domain-0, PV, PVH and HVM) Steven Haigh
2019-10-09 8:00 ` M A Young [this message]
2019-10-09 8:12 ` Steven Haigh
2019-10-09 8:22 ` M A Young
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=alpine.LFD.2.21.1910090855001.4406@algedi.dur.ac.uk \
--to=m.a.young@durham.ac.uk \
--cc=netwiz@crc.id.au \
--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).