From: Steven Haigh <netwiz@crc.id.au> To: xen-devel@lists.xenproject.org Subject: pygrub not starting first menuentry in Fedora 30 Date: Mon, 13 May 2019 20:24:28 +1000 [thread overview] Message-ID: <1557743068.2372.0@crc.id.au> (raw) 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
WARNING: multiple messages have this Message-ID (diff)
From: Steven Haigh <netwiz@crc.id.au> To: xen-devel@lists.xenproject.org Subject: [Xen-devel] pygrub not starting first menuentry in Fedora 30 Date: Mon, 13 May 2019 20:24:28 +1000 [thread overview] Message-ID: <1557743068.2372.0@crc.id.au> (raw) Message-ID: <20190513102428.l9SCidSpwTyepIEOo1IifsDpVKq1er4mTLBcAHEx7cY@z> (raw) 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
next reply other threads:[~2019-05-13 10:24 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-13 10:24 Steven Haigh [this message] 2019-05-13 10:24 ` [Xen-devel] pygrub not starting first menuentry in Fedora 30 Steven Haigh 2019-05-14 13:40 ` George Dunlap 2019-05-14 13:40 ` [Xen-devel] " George Dunlap 2019-05-14 13:49 ` Steven Haigh 2019-05-14 13:49 ` [Xen-devel] " Steven Haigh
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1557743068.2372.0@crc.id.au \ --to=netwiz@crc.id.au \ --cc=xen-devel@lists.xenproject.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).