[Bug 492895] New: kernel update incorrectly modifies Xen DomU's /boot/grub/menu.lst
http://bugzilla.novell.com/show_bug.cgi?id=492895 Summary: kernel update incorrectly modifies Xen DomU's /boot/grub/menu.lst Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PowerPC-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: pgnet.trash@gmail.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 booted to an openSUSE DomU, uname -ri 2.6.27.21-12-xen x86_64 cat /boot/grub/menu.lst default 0 timeout 1 ##YaST - generic_mbr gfxmenu (hd0,0)/message hiddenmenu ##YaST - activate title Xen 3.3.1 DomU -- openSUSE 11.1 root (hd0,0) kernel /vmlinuz-xen resume=/dev/vg0/lv_swap selinux=0 splash=silent quiet showopts nofb headless kbdtype=us text noshell initrd /initrd-xen @ kernel-update, zypper dup Retrieving repository 'Kernel_SL111' metadata [done] Building repository 'Kernel_SL111' cache [done] Loading repository data... Reading installed packages... Computing distribution upgrade... The following packages are going to be upgraded: kernel-source kernel-xen kernel-xen-base kernel-xen-extra modifies "/boot/grub/menu.lst" as cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Tue Apr 7 07:49:45 PDT 2009 default 0 timeout 1 ##YaST - generic_mbr gfxmenu (hd0,0)/message hiddenmenu ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: xen### title Xen -- openSUSE 11.1 - 2.6.27.21-15 root (hd0,0) kernel /xen.gz module /vmlinuz-2.6.27.21-15-xen resume=/dev/vg0/lv_swap kbdtype=us headless text quiet nofb selinux=0 edd=off splash=silent noshell showopts module /initrd-2.6.27.21-15-xen title Xen 3.3.1 DomU -- openSUSE 11.1 root (hd0,0) kernel /vmlinuz-xen resume=/dev/vg0/lv_swap selinux=0 splash=silent quiet showopts nofb headless kbdtype=us text noshell initrd /initrd-xen which incorrectly (1) creates a new Xen kernel stanza with kernel /xen.gz but, there _is_ no xen.gz, find /boot | grep -i xen.gz /boot/vmlinux-2.6.27.21-15-xen.gz /boot/symvers-2.6.27.21-15-xen.gz /boot/symtypes-2.6.27.21-15-xen.gz &, iiuc, that kernel /xen.gz line should not be used in the DomU's grub anyway ... (2) changes the default entry #. actually, it _fails_ to change it, but adds a new entry before the one i've defined, therefore "switching" the entry to the new/incorrect one. if not caught, the Xen DomU is rendered unbootable; of course, can be mod'd by mounting the DomU's img/drive in Dom0 & and correcting the grub entry Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=492895
User jreidinger@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c2
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=492895
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=492895
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=492895
User pgnet.dev@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c10
--- Comment #10 from pgnet Dev
http://bugzilla.novell.com/show_bug.cgi?id=492895
User jreidinger@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c11
--- Comment #11 from Josef Reidinger
has this fix been promoted to,
perl-Bootloader-0.5.0-1.1.x86_64.rpm
as well?
Yes. I check it today and it is presented. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=492895
User pgnet.dev@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c12
--- Comment #12 from pgnet Dev
(In reply to comment #10)
has this fix been promoted to,
perl-Bootloader-0.5.0-1.1.x86_64.rpm
as well?
Yes. I check it today and it is presented.
fyi, checking today, using perl-Bootloader-0.5.2-2.1 part (2) of this problem still exists; namely, "(2) changes the default entry #. actually, it _fails_ to change it, but adds a new entry before the one i've defined, therefore "switching" the entry to the new/incorrect one. if not caught, the Xen DomU is rendered unbootable; of course, can be mod'd by mounting the DomU's img/drive in Dom0 & and correcting the grub entry" -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=492895
User jreidinger@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c13
Josef Reidinger
(In reply to comment #11)
(In reply to comment #10)
has this fix been promoted to,
perl-Bootloader-0.5.0-1.1.x86_64.rpm
as well?
Yes. I check it today and it is presented.
fyi, checking today, using
perl-Bootloader-0.5.2-2.1
part (2) of this problem still exists; namely,
"(2) changes the default entry #. actually, it _fails_ to change it, but adds a new entry before the one i've defined, therefore "switching" the entry to the new/incorrect one.
if not caught, the Xen DomU is rendered unbootable; of course, can be mod'd by mounting the DomU's img/drive in Dom0 & and correcting the grub entry"
Please provide actual logs, I look what I can do, thanks -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=492895
User pgnet.dev@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c14
pgnet Dev
http://bugzilla.novell.com/show_bug.cgi?id=492895
User jreidinger@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c15
--- Comment #15 from Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=492895
User pgnet.dev@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c16
--- Comment #16 from pgnet Dev
(In reply to comment #14) This is expected behavior, if you install new kernel with same flavor (xen) then it is automatic updated. If you want use symlinks, then I think most suitable for you is set bootloader_type in /etc/sysconfig/bootloader to none and that avoid adding any new entries. Usually if user install new kernel it want use it. If you want make this behavior configurable, then open feature for that.
actually, i've no issue with having new entries added ... good to have the boot options, i suppose. the issue is to be able to NOT switch, or in other words KEEP, the same/current grub entry selection that's selected at the beginning of the process. i understand that _adding_ the entry is expected behavior. is switching the grub entry # expected behavior as well? if yes, then "configurable" feature request may be the right next step. thanks! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=492895
User jreidinger@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c17
--- Comment #17 from Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=492895
User swamp@suse.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c18
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=492895
User jreidinger@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=492895#c20
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=492895
http://bugzilla.novell.com/show_bug.cgi?id=492895#c21
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=492895
http://bugzilla.novell.com/show_bug.cgi?id=492895#c
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com