Changing the default boot selection (SUSE 10.1 w/ grub)
I'm working on an autoinstall profile for a set of machines that are all going to be running Xen, and thus need to use the -xen kernel. the .xml file has 4 sections, the first of which uses the standard -smp kernel, then the -xen kernel, then the floppy, and then the rescue system. Each of the sections works fine when selected at boot. The configurator thingy in YaST (on a running system) thinks I should be able to do something like this (trimmed quite a bit, but the point remains -- if the full xml would help, let me know and I can send it along): <bootloader> <global> <default>XEN</default> </global> <sections config:type="list"> <section> <name>SUSE Linux 10.1</name> </section> <section> <name>XEN</name> </section> <section> <name>Floppy</name> </section> <section> <name>SUSE 10.1 Rescue</name> </section> </sections> </bootloader> However, I seem to end up booted into whatever option is first in this list, regardless of what the "default" section reads. /boot/grub/menu.lst ends up with a line that looks like this: default when I think it should read default XEN or maybe default 1 So, my question: is this a bug? If so, is it a bug in the autoinstaller, or in the configurator thingy? Or am I just missing something? (I'm trying a workaround right now, just moving the XEN section to the top of the list, above the -smp section. That may work, does seem like less than ideal behavior, though...) Thanks, Ian
Hey, Uwe: Any thoughts on this one? Bug or no? On 6/15/06 1:18 PM, "Marlier, Ian" <ian.marlier@studentuniverse.com> wrote:
I'm working on an autoinstall profile for a set of machines that are all going to be running Xen, and thus need to use the -xen kernel.
the .xml file has 4 sections, the first of which uses the standard -smp kernel, then the -xen kernel, then the floppy, and then the rescue system.
Each of the sections works fine when selected at boot.
The configurator thingy in YaST (on a running system) thinks I should be able to do something like this (trimmed quite a bit, but the point remains -- if the full xml would help, let me know and I can send it along):
<bootloader> <global> <default>XEN</default> </global> <sections config:type="list"> <section> <name>SUSE Linux 10.1</name> </section> <section> <name>XEN</name> </section> <section> <name>Floppy</name> </section> <section> <name>SUSE 10.1 Rescue</name> </section> </sections> </bootloader>
However, I seem to end up booted into whatever option is first in this list, regardless of what the "default" section reads.
/boot/grub/menu.lst ends up with a line that looks like this:
default
when I think it should read
default XEN
or maybe
default 1
So, my question: is this a bug? If so, is it a bug in the autoinstaller, or in the configurator thingy? Or am I just missing something?
(I'm trying a workaround right now, just moving the XEN section to the top of the list, above the -smp section. That may work, does seem like less than ideal behavior, though...)
Thanks,
Ian
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
On Saturday 24 June 2006 05:23, Ian Marlier wrote:
Hey, Uwe: Any thoughts on this one? Bug or no?
yes, I think so. Can you create a bugreport at https://bugzilla.novell.com please? Copy and paste your mail, attach the autoyast profile and the /var/log/YaST2/y2log file please. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug
2006/6/15, Marlier, Ian <ian.marlier@studentuniverse.com>:
<bootloader> <global> <default>XEN</default> </global> <sections config:type="list"> [snip] <section> <name>XEN</name> </section> </sections> </bootloader>
However, I seem to end up booted into whatever option is first in this list, regardless of what the "default" section reads.
default
when I think it should read
default XEN
Just FYI, I think I am having a similar problem when installing LILO w/ AutoYast (SuSE 10.1 i386). I specify: <global> <default>Linux</default> </global> ... but when I actually install, Yast complains at some point that: lilo.conf: missing value for default in line 11. If I look at the system-being-installed /etc/lilo.conf file, I see in it line: default= without the section name. When I press Yes in Yast to attempt bootloader config, it shows me all the sections I've had and I just have to manually checkbox the default one. Been bit frustrating and the only thing to keep me from making fully automated installs. (That and the fact that AutoYast seems to freeze system instead of reboot, after initial install is done). The machines btw, are IBM x306m.
participants (4)
-
Emils
-
Ian Marlier
-
Marlier, Ian
-
Uwe Gansert