Xen devel - Jun 2010 - compilation errors for remus sch_queue for 2.6.31.13-pvops

Hi there.

I run Xen 4.0 with 2.6.31.13 pvops dom0 kernel.
My kernel sources reside in /usr/src/linux-2.6-xen, the xen sources in
/usr/src/xen-4.0.0.

Since i did not compile a kernel in the xen sources (just did make xen
tools install-xen install-tools) it does not automagically compile the
kmod stuff for remus.
So if i wanted to compile it while compiling xen i have to edit the
Makefile of tools/remus/kmod:
KERNELDIR = /usr/src/linux-2.6-xen

I figured i could start the compilation manually but i get the same
errors as in the normal "make xen" (of course):
tarballerina:/usr/src/xen-4.0.0/tools/remus/kmod# make -C
/lib/modules/2.6.31.13-xen0/build SUBDIRS=`pwd` modules
make: Entering directory `/usr/src/linux-2.6-xen''
CC [M] /usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.o
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:19:26: error:
linux/config.h: No such file or directory
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c: In function ‘is_foreign’:
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:51: error: implicit
declaration of function ‘xen_feature’
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:51: error:
‘XENFEAT_auto_translated_physmap’ undeclared (first use in this function)
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:51: error: (Each
undeclared identifier is reported only once
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:51: error: for each
function it appears in.)
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:52: error:
‘phys_to_machine_mapping’ undeclared (first use in this function)
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:52: error:
‘FOREIGN_FRAME_BIT’ undeclared (first use in this function)
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c: In function
‘skb_remove_foreign_references’:
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:79: error: implicit
declaration of function ‘kmap_skb_frag’
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:79: warning: assignment
makes pointer from integer without a cast
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:83: error: implicit
declaration of function ‘kunmap_skb_frag’
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c: In function ‘queue_change’:
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:177: error: implicit
declaration of function ‘netif_schedule’
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:177: error: ‘struct
Qdisc’ has no member named ‘dev’
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c: At top level:
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:195: warning:
initialization from incompatible pointer type
/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.c:196: warning:
initialization from incompatible pointer type
make[1]: *** [/usr/src/xen-4.0.0/tools/remus/kmod/sch_queue.o] Error 1
make: *** [_module_/usr/src/xen-4.0.0/tools/remus/kmod] Error 2
make: Leaving directory `/usr/src/linux-2.6-xen''

The linux/config.h part leads me to believe that this module was
intended for 2.6.18, but since xen is "shipped" with 2.6.31 this
should
not be. Especially since the fault tolerance via remus is one of the
biggest features of 4.0.

Due to a lack of documenation i am unable to compile the kernel module.
Shouldnt the module be part of the kernel and not of xen anyway?

How should i proceed, is there some documentation on how to compile the
sch_queue module for 2.6.31+ kernels?
One user on #xen on freenode told me that he had a running 2.6.32 kernel
with working remus but he used his distribution packages, so its not
impossible i guess.

On a side note: Why does the README in the remus directory point to the
remus project website? That hasnt even been updated since last year and
just has way too little information.
I would be willing to write more detailed stuff for the xensource wiki
once i get remus to work.


best regards

---
Andreas



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thursday, 17 June 2010 at 10:00, Andreas Olsowski
wrote:
> Hi there.
> 
> I run Xen 4.0 with 2.6.31.13 pvops dom0 kernel.
> My kernel sources reside in /usr/src/linux-2.6-xen, the xen sources in
> /usr/src/xen-4.0.0.
> 
> Since i did not compile a kernel in the xen sources (just did make xen
> tools install-xen install-tools) it does not automagically compile the
> kmod stuff for remus.
> So if i wanted to compile it while compiling xen i have to edit the
> Makefile of tools/remus/kmod:
> KERNELDIR = /usr/src/linux-2.6-xen
...
> The linux/config.h part leads me to believe that this module was
> intended for 2.6.18, but since xen is "shipped" with 2.6.31 this
should
> not be. Especially since the fault tolerance via remus is one of the
> biggest features of 4.0.
> 
> Due to a lack of documenation i am unable to compile the kernel module.
> Shouldnt the module be part of the kernel and not of xen anyway?
> 
> How should i proceed, is there some documentation on how to compile the
> sch_queue module for 2.6.31+ kernels?
> One user on #xen on freenode told me that he had a running 2.6.32 kernel
> with working remus but he used his distribution packages, so its not
> impossible i guess.
> 
> On a side note: Why does the README in the remus directory point to the
> remus project website? That hasnt even been updated since last year and
> just has way too little information.
> I would be willing to write more detailed stuff for the xensource wiki
> once i get remus to work.
You''re right, Remus shipped with Xen 4.0.0 only supports linux
2.6.18. xen-unstable has the patches required to run Remus on pvops
dom0. I''ll ask Keir to backport those patches to 4.0. They should be
safe and should apply cleanly, since they don''t touch non-Remus code.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thursday, 17 June 2010 at 14:18, Brendan Cully wrote:
> On Thursday, 17 June 2010 at 10:00, Andreas Olsowski wrote:
> > Hi there.
> > 
> > I run Xen 4.0 with 2.6.31.13 pvops dom0 kernel.
> > My kernel sources reside in /usr/src/linux-2.6-xen, the xen sources in
> > /usr/src/xen-4.0.0.
> > 
> > Since i did not compile a kernel in the xen sources (just did make xen
> > tools install-xen install-tools) it does not automagically compile the
> > kmod stuff for remus.
> > So if i wanted to compile it while compiling xen i have to edit the
> > Makefile of tools/remus/kmod:
> > KERNELDIR = /usr/src/linux-2.6-xen
> ...
> > The linux/config.h part leads me to believe that this module was
> > intended for 2.6.18, but since xen is "shipped" with 2.6.31
this should
> > not be. Especially since the fault tolerance via remus is one of the
> > biggest features of 4.0.
> > 
> > Due to a lack of documenation i am unable to compile the kernel
module.
> > Shouldnt the module be part of the kernel and not of xen anyway?
> > 
> > How should i proceed, is there some documentation on how to compile
the
> > sch_queue module for 2.6.31+ kernels?
> > One user on #xen on freenode told me that he had a running 2.6.32
kernel
> > with working remus but he used his distribution packages, so its not
> > impossible i guess.
> > 
> > On a side note: Why does the README in the remus directory point to
the
> > remus project website? That hasnt even been updated since last year
and
> > just has way too little information.
> > I would be willing to write more detailed stuff for the xensource wiki
> > once i get remus to work.
> 
> You''re right, Remus shipped with Xen 4.0.0 only supports linux
> 2.6.18. xen-unstable has the patches required to run Remus on pvops
> dom0. I''ll ask Keir to backport those patches to 4.0. They should
be
> safe and should apply cleanly, since they don''t touch non-Remus
code.
xen-4.0-testing.hg now contains the patches to support Remus with
pvops dom0 (thanks Keir!)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel