xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Brendan Cully <brendan@cs.ubc.ca>
To: Andreas Olsowski <andreas.olsowski@uni.leuphana.de>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: compilation errors for remus sch_queue for 2.6.31.13-pvops
Date: Wed, 23 Jun 2010 13:03:45 -0700	[thread overview]
Message-ID: <20100623200345.GC318@kremvax.cs.ubc.ca> (raw)
In-Reply-To: <20100617211818.GB2742@kremvax.cs.ubc.ca>

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!)

      reply	other threads:[~2010-06-23 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  8:00 compilation errors for remus sch_queue for 2.6.31.13-pvops Andreas Olsowski
2010-06-17 21:18 ` Brendan Cully
2010-06-23 20:03   ` Brendan Cully [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100623200345.GC318@kremvax.cs.ubc.ca \
    --to=brendan@cs.ubc.ca \
    --cc=andreas.olsowski@uni.leuphana.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).