+++ This bug was initially created as a clone of Bug #783851 +++ I've got all the xen packages installed, booting fine and working. A `yum upgrade' that updates the kernel breaks the above, and the Xen entry could not find its root filesystem anymore. This is due to the lack of a '/initramfs-xxx' module in grub.cfg, happening as a consequence of invoking grubby after the kernel update. In fact, everything was working before the upgrade, and the "module /initramfs-xxx" part was present in the Xen entry of grub.cfg. After the kernel upgrade, here's what I get: menuentry 'Fedora, with Xen hypervisor' --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-simple-86a900c9-aa88-49f1-a007-0facdf17b732' { insmod part_msdos insmod ext2 set root='hd0,msdos8' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8 20f18f9a-c006-4d92-93d2-bf053c163638 else search --no-floppy --fs-uuid --set=root 20f18f9a-c006-4d92-93d2-bf053c163638 fi echo 'Loading Xen xen ...' multiboot /xen.gz placeholder echo 'Loading Linux 3.7.6-201.fc18.x86_64 ...' module /vmlinuz-3.7.6-201.fc18.x86_64 placeholder root=/dev/mapper/host-fedora_root ro } OTOH, if I run `grub2-mkconfig | less', here's what I see: menuentry 'Fedora, with Xen hypervisor' --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-simple-86a900c9-aa88-49f1-a007-0facdf17b732' { insmod part_msdos insmod ext2 set root='hd0,msdos8' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8 20f18f9a-c006-4d92-93d2-bf053c163638 else search --no-floppy --fs-uuid --set=root 20f18f9a-c006-4d92-93d2-bf053c163638 fi echo 'Loading Xen xen ...' multiboot /xen.gz placeholder echo 'Loading Linux 3.7.6-201.fc18.x86_64 ...' module /vmlinuz-3.7.6-201.fc18.x86_64 placeholder root=/dev/mapper/host-fedora_root ro echo 'Loading initial ramdisk ...' module /initramfs-3.7.6-201.fc18.x86_64.img } So, yes, running manually grub2-mkconfig after every update that involved the kernel is a valid workaround, but it's quite uncomfortable to always have to remember doing that. This was happening in both F16 and F17, and is also happening on rawhide. See this thread: http://en.usenet.digipedia.org/thread/19183/5982/
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.