On Tue, May 14, 2019 at 11:50 PM, Lars Kurth <lars.kurth....@gmail.com> wrote:
Apologies, I mixed up some references Lars
...
[A2] https://bugzilla.redhat.com/show_bug.cgi?id=1264103 [B1] https://bugzilla.redhat.com/show_bug.cgi?id=1703700
Bug B1 here was lodged by myself. There is also a post to xen-devel titled "pygrub not starting first menuentry in Fedora 30".
I just added a comment there which I shall paste below to include those not subscribed to that BZ:
Thinking about this further - and noticing it being referenced on xen-devel mailing list, I would like to suggest the following - which may have been overlooked right now...
If the grub %post scripting checked to see if it was installing / upgrading in a Xen DomU, it could set 'GRUB_ENABLE_BLSCFG=false' in /etc/default/grub automatically. This would fix both new installs and upgrades.
The final fix would be figuring out why pygrub currently boots the *second* entry in the resulting grub.cfg - unlike how F29 worked. This may be either a fix on the grub2-mkconfig or pygrub side - I'm not quite sure yet. This would likely restore functionality completely. At least until something else more suitable is done?
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
