[yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

PGNet Dev

25 Jun 2009 25 Jun '09

21:13

starting with a grub menu.lst, cat /boot/grub/menu.lst default 0 timeout 8 gfxmenu (hd0)/boot/message title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen after a/any zypper kernel upgrade, menu.lst is modified, e.g., to, cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Thu Jun 25 16:43:29 EDT 2009 default 2 timeout 8 gfxmenu (hd0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Xen -- openSUSE 11.1 - 2.6.27.25-10 (xen) root (hd0,0) kernel /vmlinuz-2.6.27.25-10-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /initrd-2.6.27.25-10-xen ###Don't change this comment - YaST2 identifier: Original name: linux### title Xen -- openSUSE 11.1 - 2.6.27.25-10 (xen) kernel (hd0,0)/vmlinuz-2.6.27.25-10-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd (hd0,0)/initrd-2.6.27.25-10-xen title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen what specific config changes do i need to make to get the newly written configs to: (1) correctly use/write, root (hd0) instead of root (hd0,0) (2) write the kernel/initrd entries as kernel /boot/vmlinuz... initrd /boot/initrd... not, kernel /vmlinuz... initrd /initrd... fyi, config files, as default-installed are, /etc/sysconfig/bootloader ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(grub,lilo,none) ## Default: grub LOADER_TYPE="grub" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(floppy,mbr,root,boot,custom,none) ## Default: mbr # # Location of boot loader. # For making the change effect run bootloader configuration tool # # LOADER_LOCATION="" /etc/grub setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0) quit thanks! -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Show replies by date

josef reidinger

26 Jun 26 Jun

08:19

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

PGNet Dev napsal(a):

...

starting with a grub menu.lst,

cat /boot/grub/menu.lst default 0 timeout 8 gfxmenu (hd0)/boot/message

title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

after a/any zypper kernel upgrade, menu.lst is modified, e.g., to,

cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Thu Jun 25 16:43:29 EDT 2009 default 2 timeout 8 gfxmenu (hd0)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux### title Xen -- openSUSE 11.1 - 2.6.27.25-10 (xen) root (hd0,0) kernel /vmlinuz-2.6.27.25-10-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /initrd-2.6.27.25-10-xen

###Don't change this comment - YaST2 identifier: Original name: linux### title Xen -- openSUSE 11.1 - 2.6.27.25-10 (xen) kernel (hd0,0)/vmlinuz-2.6.27.25-10-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd (hd0,0)/initrd-2.6.27.25-10-xen

title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

what specific config changes do i need to make to get the newly written configs to:

(1) correctly use/write,

root (hd0)

instead of

root (hd0,0)

Because it is not correct, root set device to which is write relative path in section. it must be partition not disc.

...

(2) write the kernel/initrd entries as

kernel /boot/vmlinuz... initrd /boot/initrd...

not,

kernel /vmlinuz... initrd /initrd...

Because you have separated boot partition and perl-Bootloader detect it and correctly write section. It cannot be modified...only option is change fstab to not include separate /boot JR

...

fyi, config files, as default-installed are,

/etc/sysconfig/bootloader ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(grub,lilo,none) ## Default: grub LOADER_TYPE="grub"

## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(floppy,mbr,root,boot,custom,none) ## Default: mbr # # Location of boot loader. # For making the change effect run bootloader configuration tool # # LOADER_LOCATION=""

/etc/grub setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0) quit

thanks!

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

PGNet Dev

14:49

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

hi joseph, On Fri, Jun 26, 2009 at 1:19 AM, josef reidinger wrote:

...

...
(1) correctly use/write,

root (hd0)

instead of

root (hd0,0)

...

Because it is not correct, root set device to which is write relative path in section. it must be partition not disc.

i'm not clear as to what's "not correct". Grub's fine with partionless disks ... and, in my scenario,

...

title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

root = (hd0), NOT (hd0,0) is required. There _is_ an issue with it recognizing filesystems when on a pv-grub'd DomU (cref: Bug 516677 - grub fails to recognize filesystem on partitionless hd, in DomU booted on pv-grub Dom0).

...

...
(2) write the kernel/initrd entries as

kernel /boot/vmlinuz... initrd /boot/initrd...

not,

kernel /vmlinuz... initrd /initrd...

Because you have separated boot partition and perl-Bootloader detect it and correctly write section. It cannot be modified...only option is change fstab to not include separate /boot

then that's a problem, isn't it? again, for my situation:

...

title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

/boot/vmlinuz... is required ... if just /vmlinuz is used, the system -- not finding the kernel/initrd -- simply fails to boot. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Jozef Uhliarik

29 Jun 29 Jun

15:18

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

Hello, On Friday 26 June 2009 16:49:13 PGNet Dev wrote:

...

hi joseph,

On Fri, Jun 26, 2009 at 1:19 AM, josef reidinger wrote:

...
...
(1) correctly use/write,

root (hd0)

instead of

root (hd0,0)

Because it is not correct, root set device to which is write relative path in section. it must be partition not disc.

i'm not clear as to what's "not correct".

Grub's fine with partionless disks ... and, in my scenario,

...
title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

root = (hd0), NOT (hd0,0) is required.

There _is_ an issue with it recognizing filesystems when on a pv-grub'd DomU (cref: Bug 516677 - grub fails to recognize filesystem on partitionless hd, in DomU booted on pv-grub Dom0).

Please look at your bugreport bnc#516677 again. The error message about wrong filesystem is generated because you used disk intead of partition: from your bugreport: grub> root (hd0) root (hd0) Filesystem type unknown, using whole disk grub> If you enter root (hd0,0) instead of root (hd0) what happend?

...

...
...
(2) write the kernel/initrd entries as

kernel /boot/vmlinuz... initrd /boot/initrd...

not,

kernel /vmlinuz... initrd /initrd...

Because you have separated boot partition and perl-Bootloader detect it and correctly write section. It cannot be modified...only option is change fstab to not include separate /boot

then that's a problem, isn't it?

again, for my situation:

...
title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

/boot/vmlinuz... is required ...

if just /vmlinuz is used, the system -- not finding the kernel/initrd -- simply fails to boot.

If you use root (hd0,0) instead of root (hd0) you probably not need /boot in front of /vmlinuz-.... Have a lot of fun. Jozef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

josef reidinger

16:00

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

Jozef Uhliarik napsal(a):

...

Hello,

On Friday 26 June 2009 16:49:13 PGNet Dev wrote:

...
hi joseph,

On Fri, Jun 26, 2009 at 1:19 AM, josef reidinger wrote:

...
...
(1) correctly use/write,

root (hd0)

instead of

root (hd0,0) Because it is not correct, root set device to which is write relative path in section. it must be partition not disc. i'm not clear as to what's "not correct".

Grub's fine with partionless disks ... and, in my scenario,

...
title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

root = (hd0), NOT (hd0,0) is required.

There _is_ an issue with it recognizing filesystems when on a pv-grub'd DomU (cref: Bug 516677 - grub fails to recognize filesystem on partitionless hd, in DomU booted on pv-grub Dom0).

Please look at your bugreport bnc#516677 again. The error message about wrong filesystem is generated because you used disk intead of partition:

from your bugreport:

grub> root (hd0) root (hd0) Filesystem type unknown, using whole disk grub>

If you enter root (hd0,0) instead of root (hd0) what happend?

...
...
...
(2) write the kernel/initrd entries as

kernel /boot/vmlinuz... initrd /boot/initrd...

not,

kernel /vmlinuz... initrd /initrd... Because you have separated boot partition and perl-Bootloader detect it and correctly write section. It cannot be modified...only option is change fstab to not include separate /boot then that's a problem, isn't it?

again, for my situation:

...
title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen

/boot/vmlinuz... is required ...

if just /vmlinuz is used, the system -- not finding the kernel/initrd -- simply fails to boot.

If you use root (hd0,0) instead of root (hd0) you probably not need /boot in front of /vmlinuz-....

Have a lot of fun.

Jozef

If I good understand question, then problem is that is used in this case some partition-less technology, so grub should act on whole disc and problem is that perl-bootloader doesn't support this case and don't expect it. So if I good understand it, could you provide some resource about this technology? Also as that it is not supported It should not be reported as bug but as enhancement and new feature to features.opensuse.org. But if you use just one kernel then you can set sections to symlink /boot/vmlinux and disable perl-Bootloader to modify menu.lst during upgrade ( set BOOTLOADER_TYPE to NONE in /etc/sysconfig/bootloader ). JR -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

PGNet Dev

17:20

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

On Mon, Jun 29, 2009 at 9:00 AM, josef reidinger wrote:

...

If I good understand question, then problem is that is used in this case some partition-less technology, so grub should act on whole disc and problem is that perl-bootloader doesn't support this case and don't expect it. So if I good understand it, could you provide some resource about this technology?

re: pv-grub, http://blog.xen.org/index.php/2008/08/28/xen-33-feature-pv-grub/ as per above, the capability has been officially added to xen source, http://lists.xensource.com/archives/html/xen-changelog/2008-09/msg00135.html and is perfectly valid usage. commercial Xen hosting vendors currently use it, e.g., http://www.linode.com/wiki/index.php/PV-GRUB where, interestingly, they actually offer openSUSE as a pv-grub DomU target. which requires (hd0) be used as the grub root. i'm not certain this is a perl-bootloader issue, but rather an issue of an unpatched grub in opensuse -- i.e., one that can't handle the valid case of (hd0) without the can't-read-the-filesystem error above ...

...

Also as that it is not supported It should not be reported as bug but as enhancement and new feature to features.opensuse.org.

non-members can't submit a thing there. and membership-requests are simply not being responded to -- or at least not in a timely fashion. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Josef Reidinger

30 Jun 30 Jun

09:36

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

PGNet Dev wrote:

...

On Mon, Jun 29, 2009 at 9:00 AM, josef reidinger wrote:

...
If I good understand question, then problem is that is used in this case some partition-less technology, so grub should act on whole disc and problem is that perl-bootloader doesn't support this case and don't expect it. So if I good understand it, could you provide some resource about this technology?

re: pv-grub,

http://blog.xen.org/index.php/2008/08/28/xen-33-feature-pv-grub/

as per above, the capability has been officially added to xen source,

http://lists.xensource.com/archives/html/xen-changelog/2008-09/msg00135.html

and is perfectly valid usage. commercial Xen hosting vendors currently use it, e.g.,

http://www.linode.com/wiki/index.php/PV-GRUB

where, interestingly, they actually offer openSUSE as a pv-grub DomU target. which requires (hd0) be used as the grub root.

i'm not certain this is a perl-bootloader issue, but rather an issue of an unpatched grub in opensuse -- i.e., one that can't handle the valid case of (hd0) without the can't-read-the-filesystem error above ...

...
Also as that it is not supported It should not be reported as bug but as enhancement and new feature to features.opensuse.org.

non-members can't submit a thing there. and membership-requests are simply not being responded to -- or at least not in a timely fashion.

OK, I create it myself as https://features.opensuse.org/306592 . You can add yourself as interested person and also add some comments as I provide only basic info. JR -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Jozef Uhliarik

12:28

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

On Tuesday 30 June 2009 11:36:07 Josef Reidinger wrote:

...

PGNet Dev wrote:

...
On Mon, Jun 29, 2009 at 9:00 AM, josef reidinger wrote:

...
If I good understand question, then problem is that is used in this case some partition-less technology, so grub should act on whole disc and problem is that perl-bootloader doesn't support this case and don't expect it. So if I good understand it, could you provide some resource about this technology?

re: pv-grub,

http://blog.xen.org/index.php/2008/08/28/xen-33-feature-pv-grub/

as per above, the capability has been officially added to xen source,

http://lists.xensource.com/archives/html/xen-changelog/2008-09/msg00135.h tml

and is perfectly valid usage. commercial Xen hosting vendors currently use it, e.g.,

http://www.linode.com/wiki/index.php/PV-GRUB

where, interestingly, they actually offer openSUSE as a pv-grub DomU target. which requires (hd0) be used as the grub root.

i'm not certain this is a perl-bootloader issue, but rather an issue of an unpatched grub in opensuse -- i.e., one that can't handle the valid case of (hd0) without the can't-read-the-filesystem error above ...

...
Also as that it is not supported It should not be reported as bug but as enhancement and new feature to features.opensuse.org.

non-members can't submit a thing there. and membership-requests are simply not being responded to -- or at least not in a timely fashion.

OK, I create it myself as https://features.opensuse.org/306592 . You can add yourself as interested person and also add some comments as I provide only basic info. JR

OK I closed bug #516677 because it is feature request (FATE#306592). probably there will be necessary to update also yast2-bootloader. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

PGNet Dev

29 Jun 29 Jun

16:57

New subject: [yast-devel] how to config bootloader/grub to correctly write menu.lst modifications at kernel upgrades?

hi, On Mon, Jun 29, 2009 at 8:18 AM, Jozef Uhliarik wrote:

...

Please look at your bugreport bnc#516677 again. The error message about wrong filesystem is generated because you used disk intead of partition:

from your bugreport:

grub> root (hd0) root (hd0) Filesystem type unknown, using whole disk grub>

yes, that error is from the un-patched grub native to opensuse. the patched grub, in pv-grub works fine.

...

If you enter root (hd0,0) instead of root (hd0) what happend?

using (hd0,0) with pv-grub, the system will simply not boot, as there is no (hd0,0) ... -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

5422

Age (days ago)

5427

Last active (days ago)

List overview

Download

8 comments

4 participants

participants (4)

Josef Reidinger
josef reidinger
Jozef Uhliarik
PGNet Dev