>>> "Yoshinori K. Okuji" <[EMAIL PROTECTED]> 22.06.05 16:09:43 >>> >On Wednesday 22 June 2005 15:16, Jan Beulich wrote: >> For plain Linux that's true. For domain 0 of xen, however, this is >> different, because the domain 0 kernel is already specified as module (XEN >> itself being a multiboot image), and hence initrd needs to be specified as >> secondary module (and grub will not know this actually is an initrd). > >Use modulenounzip.
Certainly, that's needed. But it is unacceptable that I had to find out I need to do this by debugging grub (after having searched for the problem in the kernel and then in XEN for several hours), because it simply didn't tell me that it in reality didn't know how to deal with the module. That's the whole point of the bug report. Jan _______________________________________________ Bug-grub mailing list Bug-grub@gnu.org http://lists.gnu.org/mailman/listinfo/bug-grub
