[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Fedora 30 and BLSCFG changes equals non-booting DomUs.
Fedora 30 implemented Boot Loader Specification (BLS) by default for all newly installed, and any upgraded systems. This causes hell booting a DomU that is *not* configured as HVM - thus fails when not using the bootloader from within the guest. pygrub will always fail to boot these VMs. Links: Fedora change page: https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault Main Fedora BZ with lots of issues: https://bugzilla.redhat.com/show_bug.cgi?id=1652806 My bug report on new kernels not appearing in generated grub.cfg files: https://bugzilla.redhat.com/show_bug.cgi?id=1703700So far, the only workaround is to install the 'grubby-depreciated' package, set 'GRUB_ENABLE_BLSCFG=false' in /etc/default/grub, then manually re-create the grub.cfg file via: grub2-mkconfig -o /boot/grub/grub.cfg Upon a newer kernel being installed, it may or may not appear in the grub.cfg configuration - even with the above changes. As such, numerous kernel upgrades later and your installed VM might not boot at all. In numerous systems, I run grub2-mkconfig in /etc/rc.d/rc.local to avoid a completely broken VM. Not ideal. So, to start the discussion, with none of this currently being sent upstream, this is a Fedora-ism. How to handle BLS enabled guests? It also seems to be a Fedora problem with respect to kernel updates still causing problems - but that's another issue. 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |