From: "Teodor" <[EMAIL PROTECTED]>
Sent: Tuesday, July 22, 2008 11:00 PM
To: "Felix Zielcke" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: "Gavin Bravery" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Subject: Re: Bug#469578: 10_linux creates xen boot entries that don't work
The same problem I reported for grub legacy at [1]. You can read there
an explanation.
After I sent my reply to the bug report, I talked with Robert about it.
He pointed me to ask Ian Campbell about that Xen stuff.
But thanks for the old bug number.
However, this is still going to be a problem in lenny because dom0
support is missing completely and domU support is only on i386.
Why is it still a problem for grub in lenny when lenny doestn't support dom0 ?
If you're able to compile yourself a Xen kernel, you should be able to modify
your menu.lst or grub.cfg
I think a 'wontfix' tag would have been more appropriate for grub
legacy. At least in grub2 I hope it will be fixed.
grub2 currently doestn't support xen kernels
I know now that the grub lines for xen dom0 kernels should look different which
grub-legacy did.
For lenny there will for sure no Xen support in grub2, it's not the default and debian-installer only asks in expert mode to install
it.
Patches for it are appreciated
It's not good btw. to check just for *xen* in the filename.
It doestn't need to be true, e.g. when you compile your own Xen kernel.
So the best would be to check for this PARAVIRT or XEN stuff in config-<kernel> if that kernel is a Xen one or not.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
