On Tue, Sep 18, 2018 at 6:48 PM, Adam Williamson
<adamwill(a)fedoraproject.org> wrote:
On Tue, 2018-09-18 at 18:45 -0600, Chris Murphy wrote:
> On Tue, Sep 18, 2018 at 6:37 PM, Adam Williamson
> <adamwill(a)fedoraproject.org> wrote:
> > On Tue, 2018-09-18 at 20:09 +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 18-09-18 17:28, Chris Murphy wrote:
> > > > On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewski-Szmek
> > > > <zbyszek(a)in.waw.pl> 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(a)redhat.com> 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.
> >
> > Note, I can't reproduce this with an install of Beta RC3 Workstation
> > live to a BIOS vm in virt-manager. F8 works every time to bring up the
> > boot menu (yes, I checked that if I *don't* press F8, the boot menu
> > *doesn't* show up, too).
> >
> > Perhaps this is Silverblue-specific somehow?
>
> No I reproduced the problem with beta 1.3 in both BIOS and UEFI VMs
> using virt-manager. I tried ESC, Shift, F8, space - both holding, and
> rapid pressing. *shrug*
That's odd, it definitely works for me...
given the confusion here, I'm sending the RC4 request without grub2
-58. If we wind up finding more blockers, maybe it can go into RC5...
I'm not finding a criterion requiring either the key reveal feature to
work; or for the failed boot detection to work. Seems like that might
need a tweak. Sure, anything that breaks boot and ability to login is
itself a blocker anyway.
--
Chris Murphy