After
grub2-reboot uefi-firmware
grub directly boots the bios without even briefly showing the menu. grub2-reboot did give a warning, but i bravely presumed i could still boot by grabbing the boot menu. But boot_once doesn’t show the menu and sets timeout=0. Does that leave some way to grab the menu? Or boot? Other than go find a bootable thumb drive?
grub2-reboot sets next_entry (not boot_once) and grub clears it on next boot - if environment block is writable at boot time. If it is not, yes, you need to boot from some external medium.
looks like a design bug to me, why should next_entry/boot_once prevent access to the grub menu? That sets up a classic case of catch 22, “next boot” can’t happen until it can boot up, bootup can’t happen until “next boot” happens. Umm…
Is this a bare metal instance?
Or is this related to your TW KVM instance (I read another post you have related to a KVM) ?
Do we simply go enter a bug at bugzilla.opensuse.org, or is there some clever method to promote a forum article to a bug?
Yes i have prior guests where either the guest is headless tumbleweed or the host is tumbleweed, but this is my first and so far only where both the host and the guest are kde tumbleweed.
More accurately the kvm host is headless tumbleweed and both the guest and the display host are kde tumbleweed.
You can probably get around the problem by removing “/boot/grub2/grubenv”.
oops…i was thinking of my other post…
A desktopless bare metal fileserver kvm host.
i ‘promoted’ this to an opensuse bug.
OT:
If it was true openSUSE, you would not have used bugzilla.suse.com to report it, or provide a link to the report using a bugzilla.suse.com URL. It’s technically perfectly OK to do as you did, but it has a sad visual impact on the openSUSE project. It would do the project well if everyone stopped forumizing bugzilla.suse.com URLs. I prevent my browsers from opening them by redirection in my hosts file:
0.0.0.0 buzilla.suse.com
It makes opening such new bugs a minor hassle, but it avoids browser history bloat.
http://bugzilla.opensuse.org/show_bug.cgi?id=1210969
c.f.: bug 1210603
c.f.: bug 1081441
You are the only one who perceives it his way and spams every possible communication channel with these posts.
You are perfectly aware that openSUSE is 99% SUSE and most bug reports are handled by SUSE employees anyway (with very few exceptions). Blocking site bugzilla.suse.com is not going to change it in any way.
ah. oops. i encourage anyone with edit rights to edit it to ‘opensuse’.
openSUSE is the proper name. Not opensuse.
works perfectly well in URLs, however it changes itself right back to “opensuse”
indeed, however, grub can’t delete. granted perhaps you can boot some other way eg with a thumb drive, but you need to boot first, which is the point of the OP.
This wasn’t about the peculiarities in URLs, it was about using the proper name for the distribution. And it is all over the web sites of the distribution, thus not difficult to at least type it without typos.
And it was completely irrelevant because “opensuse” in this case referred to URL and not to distribution.
Was that clear? scrolling back I end at a mentioning of “it”. And that is it.
Yes, if you read this topic from the beginning. No if you just look for familiar keywords.
Unfortunately, even in mailing lists useful quoting became rather exception than the rule. And in web forums users simply add another comment without any attempt to indicate to which previous statement it refers.