Just as a heads up, there seem to be a couple of issues with grubby and the grub.cfg submenus used for Xen right now. My system still boots after triggering any of these but it's usually not running Xen and not always running the kernel I want it to be running.
Kernel submenu entries aren't updated w/ kernel updates: - https://bugzilla.redhat.com/show_bug.cgi?id=748551 This can be worked around by regenerating grub.cfg @ every kernel update ('grub2-mkconfig -o /boot/grub2/grub.cfg')
There are a couple other grubby issues that I haven't hit naturally yet (not difficult to provoke, though). Both can be worked around by regenerating grub.cfg after making kernel changes but before rebooting.
- Extra entries are being removed from grub.cfg @ kernel pkg removal * https://bugzilla.redhat.com/show_bug.cgi?id=744717 * I haven't personally seen this during kernel removal @ upgrade time but it's something to watch out for if you are removing kernels
- Whitespace is removed from grub default once grub.cfg is processed by grubby. * https://bugzilla.redhat.com/show_bug.cgi?id=742720 * 748551 also stomps on the default in grub.cfg, so I haven't seen this yet but it could show up.
On Mon, 24 Oct 2011, Tim Flink wrote:
Just as a heads up, there seem to be a couple of issues with grubby and the grub.cfg submenus used for Xen right now. My system still boots after triggering any of these but it's usually not running Xen and not always running the kernel I want it to be running.
I have seen what I suspect is another one though I haven't investigated fully yet to confirm it. I think that if you delete a kernel with a xen entry it can remove a submenu opening clause but not the corresponding closing } which is bad if you have the xen hypervisor installed in a guest as it upsets pygrub.
Michael Young
On Mon, 24 Oct 2011 20:56:47 +0100 (BST) M A Young m.a.young@durham.ac.uk wrote:
On Mon, 24 Oct 2011, Tim Flink wrote:
Just as a heads up, there seem to be a couple of issues with grubby and the grub.cfg submenus used for Xen right now. My system still boots after triggering any of these but it's usually not running Xen and not always running the kernel I want it to be running.
I have seen what I suspect is another one though I haven't investigated fully yet to confirm it. I think that if you delete a kernel with a xen entry it can remove a submenu opening clause but not the corresponding closing } which is bad if you have the xen hypervisor installed in a guest as it upsets pygrub.
Yeah, that's 744717. The bug isn't incredibly clear and I didn't do a very good job of summarizing it. If you look at the before and after grub.cfg files, you can see it though.
How often would that happen in a guest? I don't think that I have submenu entries in any of my DomUs.
Tim
-
M A Young -
Tim Flink