From: Brendan Cully Subject: Re: [PATCH 0 of 3] Remus: control tool Date: Fri, 13 Nov 2009 13:36:27 -0800 Message-ID: <20091113213627.GD11642@kremvax.cs.ubc.ca> References: <20091113141859.GB23952@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20091113141859.GB23952@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: andy@cs.ubc.ca, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Friday, 13 November 2009 at 09:18, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 12, 2009 at 05:10:21PM -0800, Brendan Cully wrote: > > The following patch series integrates the Remus control layer into > > Xen. It provides a single user-visible script ("remus") to activate > > Remus on a guest virtual machine, and the libraries required by that > > script. > > Cool. Looking forward to read them. > > > > Network buffering requires the linux IMQ (http://linuximq.net) patch > > to be applied to dom0. I'll mail the upstream version that applies to > > the linux-2.6.18-xen.hg tree separately. > > Is there a 2.6.31.x variant of the code? Are there plans to submit the > patches to LKML? I haven't tried to get this working on pvops yet, but it's simple in theory: domU ought to work now, albeit somewhat slowly since the pvops domU doesn't support suspend requests over a dedicated event channel. Cooking up a patch for this is probably not too hard. dom0 requires nothing but the upstream IMQ patch, and blktap2 support, which I am told it currently lacks, but I'm sure it will get in the not-too-distant future.