Hello, Am Mittwoch, den 06.08.2008, 21:41 +0100 schrieb 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).
Well the patch was anyway made only for people like the reporter who just want to have that update-grub doestn't add any Xen kernel. But if they can be booted like any normal kernel then yes this is a bit wrong. I just used the config entrys which are in grub-legacy's update-grub for xen kernels, which adds kernels with these as Xen ones not normal ones. > > 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. As I already said, I look into it further when Debian has again a kernel build with Dom0 support. For lenny Xen support in grub2 is too late and grub2 is anyway still not the default. So luckly we have enough time for lenny+1 and with grub2 we shouldn't support any old method used. Robert didn't like the idea to copy the whole 10_linux to a 10_xen and thus duplicating the whole logic. Good to know that the new style ones can just run fine with a normal entry created for them, you just can't have DomU's then. In #419157 Robert said a year ago, that the Xen team should handle the 10_xen They should it know anyway better then us how to make Xen entrys But probable I'll bring it up on grub-devel, maybe this should be even upstream supported. Thanks for reading and replying to this bug report :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
