[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] /sys/hypervisor entries for Xen (Domain-0, PV, PVH and HVM)


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Steven Haigh <netwiz@xxxxxxxxx>
  • Date: Wed, 09 Oct 2019 15:14:56 +1100
  • Delivery-date: Wed, 09 Oct 2019 04:15:24 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

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.

Any comments either here or via the BZ report above would be welcome.

Steven Haigh

📧 netwiz@xxxxxxxxx     💻 https://www.crc.id.au
📞 +613 9001 6090       📱 +614 1293 5897




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.