On Wed, Jul 19, 2006 at 11:00:38PM +0200, Manuel Bouyer wrote:
> On Wed, Jul 19, 2006 at 02:59:37PM -0500, reed%reedmedia.net@localhost wrote:
> > > Well, modules are always compiled without options in the distrib.
> > > As Xen kernels are compiled with debug options, these are incompatible.
> > > You'll have to rebuild a LKM with these options, but I don't know the
> > > details.
> >
> > So I retrieved netbsd-3 via cvs. On my NetBSD/i386 3.99.21 build system, I
~~~ snip ~~~
> >
> > So what is the correct way to build a pf.o?
pf.o is somehow inherently incompatible with a XENU kernel, with or
without DEBUG,DIAGNOSTIC. I have a very similar panic when I load
a standard pf.o into the kernel I use (see below).
> >
> > Does anyone use kernel modules with Xen?
Yes. NetBSD 3.0/Xen 2.0. Both in Dom0 and DomU. In this case the module
is nnpfs_mod.o from the Arla (v. 0.41 and 0.43) AFS client. I usually
will use a custom xen kernel without DEBUG,DIAGNOSTIC so that the module
will work with both a i386 and xen kernel.
The only trouble I've had was when I upgraded to a netbsd-3 kernel and
arla 0.43, after rebuilding nnpfs_mod.o against the new sources
my AFS access will go out to lunch after a few hours, but no panics.
Finding the actual problem has not made it's way to the top of the
to do list yet.
>
> I don't think so. In fact, I think there's too much differences between
> i386 and xen kernel headers to be able to share LKMs between i386 and Xen.
I really hope that this isn't actually the case. Having AFS access is
essential.
> The lkms need to be built with includes from arch/xen. But I don't know
> what needs to be changed in the Makefile for that. Maybe you need to
> change MACHINE and/or MACHINE_ARCH make variables
I built nnpfs_mod.o no differently than I would on any other architecture.
Of course, this module is basically a character device and a file system,
not a module that becomes part of the networking subsystem.
Jonathan Kollasch
Attachment:
pgpEs3HE8LMSL.pgp
Description: PGP signature