[Bug 774666] New: grub2 does not offer a Xen entry after installing hypervisor and tools
https://bugzilla.novell.com/show_bug.cgi?id=774666 https://bugzilla.novell.com/show_bug.cgi?id=774666#c0 Summary: grub2 does not offer a Xen entry after installing hypervisor and tools Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: ohering@suse.com QAContact: jsrain@suse.com CC: carnold@suse.com Found By: Outsourced Testing Blocker: --- After a fresh 12.2-rc2 installation I installed the 'Hypervisor and Tools' with yast. But after reboot there was no xen entry offered. I see /etc/grub.d/20_linux_xen in grub.cfg, but no entries. If I run the script menually it produces this output and does exit with error code 0: ... optiplex:~ # env LC_ALL=C /etc/grub.d/20_linux_xen Found linux image: /boot/vmlinuz-3.4.6-1.1-xen Found initrd image: /boot/initrd-3.4.6-1.1-xen menuentry 'GNU/Linux, with Xen hypervisor' --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-simple-' { /usr/sbin/grub2-probe: error: cannot find a GRUB drive for . Check your device.map. echo 'Loading Xen 4.1.2_17-5.2.3 ...' multiboot /boot/xen-4.1.2_17-5.2.3.gz placeholder echo 'Loading Linux 3.4.6-1.1-xen ...' module /boot/vmlinuz-3.4.6-1.1-xen placeholder root= ro echo 'Loading initial ramdisk ...' module /boot/initrd-3.4.6-1.1-xen } submenu 'Advanced options for GNU/Linux (with Xen hypervisor)' $menuentry_id_option 'gnulinux-advanced-' { submenu 'Xen hypervisor, version 4.1.2_17-5.2.3' $menuentry_id_option 'xen-hypervisor-4.1.2_17-5.2.3-' { menuentry 'GNU/Linux, with Xen 4.1.2_17-5.2.3 and Linux 3.4.6-1.1-xen' --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-3.4.6-1.1-xen-advanced-' { /usr/sbin/grub2-probe: error: cannot find a GRUB drive for . Check your device.map. echo 'Loading Xen 4.1.2_17-5.2.3 ...' multiboot /boot/xen-4.1.2_17-5.2.3.gz placeholder echo 'Loading Linux 3.4.6-1.1-xen ...' module /boot/vmlinuz-3.4.6-1.1-xen placeholder root= ro echo 'Loading initial ramdisk ...' module /boot/initrd-3.4.6-1.1-xen } .... I'm not sure why the cmdline has an empty root= and puts 'ro' in there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c1
--- Comment #1 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c2
Charles Arnold
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c3
--- Comment #3 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c4
--- Comment #4 from Michael Chang
Yast2-vm just installs kernel-xen and the xen packages and the grub magic happens elsewhere. If something new needs to be done in yast2-vm for grub2, someone will need to let me know.
I think after xen package installation we have to trigger grub2 to update it's config thus it could be updated with installed xen hypervisor. Now it only triggered by kernel package installation (in %post script calls update_bootloader or something like that) and xen sections are missing unless you trigger grub2 config update again (via yast2 bootloader or grub2-mkconfig manually). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c5
--- Comment #5 from Michael Chang
Installing the tools, then opening the Bootloader setup once gives a xen entry.
Another thing: Too bad, now there is appearently no obvious way to make xen (or any other in the list) the default boot entry. 'deault N' was certainly a weird way in menu.lst, but now there is appearently none.
/etc/defauklts/grub suggests that 'GRUB_DEFAULT=saved' reuses the currently used entry, but thats not the case.
Use "saved" is we have to call grub2-reboot for setting bootonce. And we should use grub2-set-default to set your default entry and 'grub2-editenv list' to observe the environment settings. Blame to grub2, the config is too complicated by introducing the nasty (most of time useless) "nested submenu" feature. With submenu the number is not useful if you want to address the boot entry in subment, it counts only the 1st layer of boot menu. To ease the task of doing that, I have a script to translate the boot number to menuentry path that could feed to grub2-set-default https://build.opensuse.org/package/view_file?file=grub2once&package=grub2&project=home%3Amichael-chang%3Abnc_771587&rev=c5de531462bed677a20b0034330b3cd4 For ex the menuentry is 4 (in order of appearance) $ grub2-set-default `grub2once --show-mapped 4` -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c6
--- Comment #6 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c7
--- Comment #7 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c8
--- Comment #8 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c9
Jiri Srain
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c10
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c11
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c12
--- Comment #12 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c13
--- Comment #13 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c14
Uwe Geuder
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c15
--- Comment #15 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c16
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c17
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c18
--- Comment #18 from Uwe Geuder
$ grub2-mkconfig -o /boot/grub2/grub.cfg
That patch is to solve the problem *during* the package installation,
Thanks Michael, this makes sense to me. I did not need to run the command manually anymore. After installing a kmp package to resolve https://bugzilla.novell.com/show_bug.cgi?id=771392 the missing menu entries appeared automatically. Probably that package has called grub2-mkconfig during its installation. (Booting to Xen kernel from that entry does not work. There is a problem to unlock my LUKS encrypted LVM volume containing root and home. But I guess this needs to be reported as a separate issue, I don't clutter up this report) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c19
--- Comment #19 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c20
--- Comment #20 from Uwe Geuder
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c21
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=774666
https://bugzilla.novell.com/show_bug.cgi?id=774666#c22
--- Comment #22 from Luis Rodriguez
http://bugzilla.novell.com/show_bug.cgi?id=774666
Thomas Renninger
http://bugzilla.novell.com/show_bug.cgi?id=774666
Luis Rodriguez
For the records: #bnc897901 is fixed in factory dracut package.
If I understand correctly, this one can be closed then as well?
No, someone will need to test removing the work around with all the respective packages updated and ensuring the work around is no longer required. Doing so will satisfy a proper fix for the work around and also address my work around on top of the work around that disables the work around :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=774666
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
http://bugzilla.novell.com/show_bug.cgi?id=774666#c42
--- Comment #42 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
http://bugzilla.novell.com/show_bug.cgi?id=774666#c43
--- Comment #43 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=774666
http://bugzilla.novell.com/show_bug.cgi?id=774666#c44
--- Comment #44 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com