Bug#469578: 10_linux creates xen boot entries that don't work

[Ian Campbell]

On Thu, 2008-07-31 at 15:41 +0200, Felix Zielcke wrote:
> Attached is now a patch which ignores Xen kernels,

Unless I am misreading the patch it appears to ignore CONFIG_PARAVIRT=y
type Xen kernels which is wrong -- these kernels also boot native and so
a normal entry should be created for them. This is useful in both dom0
(since it can boot native) and in domU (since native-style entries are
used there).

> It seems [0] that Xen Dom0 support will be soon in the official kernel.
> I don't know anything about the config options which will be then used.

In this case there would need to be a _second_ entry created in domain 0
(dom0 vs. domU detected via presence of a hypervisor binary) in addition
to the normal native entry.

> So it could be that the config options aren't that right in the future,
> when there's again a Xen Dom0 kernel in Debian or if you compile your
> own.
> 
> But if anyone wants to work on implementing Xen specific handling for
> grub2 then please base your work on that patch now.
> Don't use the filename as I first did.
> 
> [0] http://lists.debian.org/debian-devel/2008/07/msg01012.html
> _______________________________________________
> Pkg-grub-devel mailing list
> Pkg-grub-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
-- 
Ian Campbell

Mommy, what happens to your files when you die?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20080806/0c9307f8/attachment.pgp