Hi,
On 18-09-18 17:28, Chris Murphy wrote:
On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewski-Szmek
<zbyszek@xxxxxxxxx> wrote:
On Tue, Sep 18, 2018 at 08:36:32AM -0600, Chris Murphy wrote:
On Tue, Sep 18, 2018 at 4:56 AM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
Hi,
On 18-09-18 01:12, Chris Murphy wrote:
I've got a Fedora 29 Silverblue installation in a VM.
What kind of VM is it?
qemu/kvm using virt-manager
I am not using direct kernel boot. The grub command line, which is the
only thing that has that command line, is passed onto the kernel and I
can see that in dmesg - which would not be the case with direct kernel
boot, if grub were being skipped.
Ok, I've managed to reproduce this in a classic BIOS boot using VM and
then after updating grub2 to 2.02-58 and running grub2-mkinstall the
problem went away. It looks like this somehow for broken in one specific
grub2 build and then fixed again with anyone from the rhboot group
realizing it was broken in the interim.
Please try upgrading to grub2-2.02-58 from updates-testing and if
you are using classic BIOS boot also run grub2-mkinstall after this.
Regards,
Hans
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
