Bug#500336: grub - Misguides Xen images

[Felix Zielcke]

Hi,

sorry for not replying directly but somehow the mails of this report got lost for me,

>update-grub adds 2.6.26-1-686-bigmem with a Xen hypervisor to the grub
>config. This image does not support to be loaded as initial domain by
>the hypervisor.

I don't get this Xen stuff
There is this [0] message from Ian Campbell which says that there's no way to dertermine
if a CONFIG_PARAVIRT=y + CONFIG_XEN=y runs in a Dom0 or not.

# diff -u config-2.6.26-1-*|egrep 'XEN|PARAVIRT'
 CONFIG_PARAVIRT_GUEST=y
 CONFIG_XEN=y
 CONFIG_XEN_MAX_DOMAIN_MEMORY=8
+CONFIG_XENCTRL=y
 CONFIG_PARAVIRT=y
-CONFIG_XEN_BLKDEV_FRONTEND=m
+CONFIG_XEN_BLKDEV_FRONTEND=y
-CONFIG_NETXEN_NIC=m
-CONFIG_XEN_NETDEV_FRONTEND=m
+CONFIG_XEN_NETDEV_FRONTEND=y
 CONFIG_HVC_XEN=y
 CONFIG_XEN_FBDEV_FRONTEND=y
 CONFIG_XEN_BALLOON=y
 CONFIG_XEN_SCRUB_PAGES=y

So should we also grep for CONFIG_XENCTRL=y to be more on the safe side that this kernel can be loaded
with the Xen hypervisor?
There was a bugreport that we shouldn't look for *-xen-* in the filename, because some other thing uses xen too
which has nothing to do with the Xen virtualization if I remember correctly and for custom kernels this wouldn't work anyway.