On Mon, 29 Nov 2010, W. Michael Petullo wrote:

> As far as I can tell, Fedora's grubby does not yet support the GRUB
> syntax required by Xen, e.g.,
>    title Fedora (
>        root (hd0,0)
>        kernel /xen-4.0.1.gz
>    ==> module /vmlinuz- ...
>    ==> module /initramfs-
> I don't think it supports multiple "module" keywords.
> I am presently working on extending grubby to allow something like the
> following (note that the --add-kernel parameter name might change):
> grubby --add-multiboot=/boot/xen.gz --mbargs="[xen arguments]" \
>       --add-kernel=/boot/vmlinuz- \
>       --args="[kernel arguments]" \
>       --add-kernel=/boot/initramfs- \
>       --title="Xen Hypervisor"
> Does this make sense?

Before you go too far I suggest you talk to the Fedora maintainer(s) and 
the upstream maintainer(s) of grubby (who I think in this case are the 
same) because they are the ones that have to be convinced to accept the 
changes, and they may have ideas on the best way to do it.

> How could we tie this into anaconda kernel upgrades? I am thinking of
> adding something to /etc/sysconfig/kernel that new-kernel-pkg would
> look for. If the flag is present, then new-kernel-pkg could use the
> extended grubby syntax. The Fedora Wiki's XenPvopsDom0 document mentions
> /etc/sysconfig/xen instead, is this up to date? Should we use this
> instead of /etc/sysconfig/kernel?

That page https://fedoraproject.org/wiki/Features/XenPvopsDom0 isn't 
particularly up to date and the first stage may be to update it and then 
go through the process of getting it accepted as a feature, as other 
maintainers are more likely to be receptive to changes in that case.

Currently that page mentions both /etc/sysconfig/kernel and 
/etc/sysconfig/xen . I would imagine that /etc/sysconfig/kernel is read 
already by new-kernel-pkg so it might be simpler to add a configuration 
option there.

        Michael Young
xen mailing list

Reply via email to