Bug 148461

xen is a bit different in respect that it needs a slightly differently looking boot entry.  Not sure whenever update-bootloader can handle that, Jiri?

Jack has taken over maintenance of perl-Bootloader.

Hmh. As you didn´t say _what_ you need, I regret that I cannot give you a perfectly matching answer. So the best answer might be the output of current
'update-bootloader --man'

NAME
       update-bootloader - update/change bootloader configuration using
           Bootloader::Tools perl module

SYNOPSIS
       update-bootloader [operation] [options]

       operation is one of --add, --remove or --refresh.

       valid options are --help, --man, --image <file>, --initrd <file>, --default, --previous, --name <string>, --force.

OPERATIONS
       --add   add an new image section.  Needs a call to --refresh to take effect.

       --remove
               remove the specified image section.  Needs a call to --refresh to take effect.

       --refresh
               activate the new config e.g. write boot loader to disk

PARAMETER
       --help  Print a brief help message and exits.

       --man   Prints the manual page and exits.

       --image file
               specify path to kernel image

       --initrd file
               specify path to initial ramdisk or ramfs

       --default
               let the new section to be added be the default section. Only allowed together with --add operation

       --previous
               set some usuable defaults for image, initrd and name when

       --name string
               specify the name of the section to be added/removed

       --force dont complain, just do the right thing

DESCRIPTION
       update-bootloader will let you modify your bootloader configuration using Bootloader::Tools perl module.

--------------

Please note that you have to call update-bootloader --refresh to activate your
changes to the bootloader config.

Using --force is also a good idea -> be quiet and do not break on errors

Created attachment 68110 [details]
grub config file with xen entry as created by yast2-bootloader

additional info: xen uses the boot protocol "multiboot" invented by the grub guys.  "kernel" is xen itself, then two "module" entries follow with xen kernel and initrd.  booting xen with lilo doesn't work.  we have xen on i386 and x86_64 only at the moment.

had to change the interface in Tools.pm and the usage of update-bootloader.
This is still under debugging as it does not work right yet.

However the interface has settled. I the xen case updat-bootloader will be used right as for a regular image section but one has to give an additional
--xen option in the call.

Please add that option to the appropriate places and assign the bug to me
afterwards for a final perl-bootloader commit.

with a few more changes it seems to work now. Tested sucessfully:

./update-bootloader --xen --add --image /boot/vmlinuz-xen \
    --initrd /boot/initrd-xen --name XEN

./update-bootloader --xen --remove --image /boot/vmlinuz-xen

Thus it´s done from my side.

Puzzled by the *two* update-bootloader calls in post.sh, especially the one outside "case @flavor@ ... esac".  agruen?

Created attachment 70367 [details]
This should add --xen as appropriate.

One of the calls is for the *.previous symlinks; the other is for the kernel being installed. I noticed that the --add call in postun.sh is unneeded as well now (the main bootloader entry is never removed).