WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 0 of 2] Remus: support for pvops dom0

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 2] Remus: support for pvops dom0
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Thu, 15 Apr 2010 10:58:06 -0700
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 15 Apr 2010 10:59:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19399.7043.297474.894527@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Ian.Jackson@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy@xxxxxxxx
References: <patchbomb.1271281846@xxxxxxxxxxxxxxxxx> <19399.7043.297474.894527@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2010-03-22)
On Thursday, 15 April 2010 at 14:58, Ian Jackson wrote:
> Brendan Cully writes ("[Xen-devel] [PATCH 0 of 2] Remus: support for pvops 
> dom0"):
> > These two patches update the Remus network buffering code to work with
> > newer kernels, including the pvops tree.
> 
> Excellent.
> 
> > Built and run, but not extensively tested (I'm still working on some blktap2
> > issues on the disk replication side).
> 
> I haven't looked at the code for the "remus" utility, but: How hard is
> it going to be to port it to libxl ?  I think remus is too exciting a
> feature to be left to rot with xend.

Thanks :)

Remus doesn't really use xend at all. It has its own bindings to libxc
and reimplements the migration control layer. I'd had tighter
integration with xend on my TODO list, but it sounds like I may not
need to do that any more.

I haven't been paying close attention to the libxl patches flying by
on the list, but it looks like the area where libxl and Remus might
interact in the short term is your cleanups to the save image
format. Off the top of my head, I remember having to hack up a
slightly different stream format for HVM because the qemu blob had no
length prefix.

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