I just tried building a debian xen0 kernel with the standard make-kpkg tools and the packages from www.terrabox.com, and while it gave me a resulting package, I noted the following: . resulting package name is kernel-xen0-2.6.9_1_i386.deb where I would have expected kernel-image-2.6.9... . no initrd generated on install even though I requested one on the make-kpkg commandline . enabling pnp bios support caused a failed compile. Probably don''t want this anyway though as I understand there is no way to access pnp bios info from xen. Is this normal? Thanks James
If you use the xenlinuxbuilder it gets everything correct except that it doesn''t do debs just yet. ;-P I think you need to use the subarch parameter to get the xen specific subarch of i386. On Sun, 2004-12-12 at 16:41 +1100, James Harper wrote:> I just tried building a debian xen0 kernel with the standard make-kpkg > tools and the packages from www.terrabox.com, and while it gave me a > resulting package, I noted the following: > > . resulting package name is kernel-xen0-2.6.9_1_i386.deb where I would > have expected kernel-image-2.6.9… > > . no initrd generated on install even though I requested one on the > make-kpkg commandline > > . enabling pnp bios support caused a failed compile. Probably don’t > want this anyway though as I understand there is no way to access pnp > bios info from xen. > > > > Is this normal? > > > > Thanks > > > > James > > > >-- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
James Harper wrote:> I just tried building a debian xen0 kernel with the standard make-kpkg > tools and the packages from www.terrabox.com, and while it gave me a > resulting package, I noted the following:> . resulting package name is kernel-xen0-2.6.9_1_i386.deb where I would > have expected kernel-image-2.6.9...This is intentional, I believe, but I''m not sure if it is correct. Obviously kernel-image-2.6.9 is different from kernel-xen0-2.6.9 and needs to contain different scripts and be handled differently. But, since the kernel version is still the determining factor in many paths (like /lib/modules/2.6.9), the package would need to conflict with every other kernel by the same version. So, I''m really not sure what would be the best approach here.> . no initrd generated on install even though I requested one on the > make-kpkg commandlineI would say this is a bug - the Xen postinst scripts are not those of normal i386 kernels I believe, so they need fixing. I have never tried initrd kernels with Xen.> . enabling pnp bios support caused a failed compile. Probably don''t want > this anyway though as I understand there is no way to access pnp bios > info from xen.There are things in the kernel config, which if enabled, cause the compilation to fail. The Xen guys probably will be fixing these as they crop up. And I would *guess* that with Xen 2.1, accessing the PnP bios info from Xen should work as with a normal machine.> Is this normal?Well, normal - I guess. -- Naked ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Mon, 2004-12-13 at 14:10 +0200, Nuutti Kotivuori wrote:> James Harper wrote: > > I just tried building a debian xen0 kernel with the standard make-kpkg > > tools and the packages from www.terrabox.com, and while it gave me a > > resulting package, I noted the following: > > > . resulting package name is kernel-xen0-2.6.9_1_i386.deb where I would > > have expected kernel-image-2.6.9... > > This is intentional, I believe, but I''m not sure if it is > correct. Obviously kernel-image-2.6.9 is different from > kernel-xen0-2.6.9 and needs to contain different scripts and be > handled differently. But, since the kernel version is still the > determining factor in many paths (like /lib/modules/2.6.9), the > package would need to conflict with every other kernel by the same > version. So, I''m really not sure what would be the best approach here.This is why I use kver-extraver-privmode as the uname -r in xenlinuxbuilder. You can specify extraversion in make-kpkg and avoid this kind of conflict in most things.> > > . no initrd generated on install even though I requested one on the > > make-kpkg commandline > > I would say this is a bug - the Xen postinst scripts are not those of > normal i386 kernels I believe, so they need fixing. I have never tried > initrd kernels with Xen.Probably because the initrd creation scripts for i386-xen don''t exist yet. Probably just a symlink to the normal i386 in debian would do the trick. :)> > > . enabling pnp bios support caused a failed compile. Probably don''t want > > this anyway though as I understand there is no way to access pnp bios > > info from xen. > > There are things in the kernel config, which if enabled, cause the > compilation to fail. The Xen guys probably will be fixing these as > they crop up.I''m hitting a few myself at compile time as I refine a +kitchen-sink config for the debianized kernels that I haven''t released yet. I''ll release info when I get back to tweaking the sets.> > And I would *guess* that with Xen 2.1, accessing the PnP bios info > from Xen should work as with a normal machine. > > > Is this normal? > > Well, normal - I guess. > > -- Naked > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel-- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > This is why I use kver-extraver-privmode as the uname -r in > xenlinuxbuilder. You can specify extraversion in make-kpkg and avoid > this kind of conflict in most things. > > > I would say this is a bug - the Xen postinst scripts are not thoseof> > normal i386 kernels I believe, so they need fixing. I have nevertried> > initrd kernels with Xen. > > Probably because the initrd creation scripts for i386-xen don''t exist > yet. Probably just a symlink to the normal i386 in debian would do the > trick. :)I can test that pretty easy if you tell me how to do it. One other thing I noticed was that a second make-kpkg produced a kernel package with almost no modules, and a third make-kpkg had even less modules and didn''t actually do any building. I may have done something wrong to trigger this but it also may be a bug. Thanks James ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel