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