There seems to be some changes in Fedora 30 that cause the second boot
entry in grub.cfg to be booted instead of the first.
This means that Fedora 30 systems either always boot into an older
kernel, or in the case of systems with only one kernel installed, the
rescue image.
There also seems to be some new issues with the move to BLSCFG -
however it seems a new requirement is to have
GRUB_ENABLE_BLSCFG="false" in /etc/default/grub. This causes
grub2-mkconfig to work correctly and spit out a grub.cfg file that
pygrub can then use.
Is this a bug in pygrub, or a problem with how Fedora 30 generates a
grub.cfg?
I tried to pick through pygrub - but couldn't quite follow the python
logic to see where the default boot option is selected.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
