Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] (resent) NUMA node migration

To: Andre Przywara <andre.przywara@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] (resent) NUMA node migration
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Sat, 22 Dec 2007 00:53:15 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 21 Dec 2007 16:54:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <476C40BE.1030907@xxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <476C40BE.1030907@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Dec 21, 2007 at 11:39:58PM +0100, Andre Przywara wrote:

> accordingly. Only changes Python code in xend. I hope that the patch
> doesn't break XenAPI compatibility (adding a parameter seems fine?).
> 
> # xm migrate --live --node=<nodenr> <domid> localhost
> <nodenr> is the number as shown with 'xm info' under node_to_cpu
> 
> I am aware that using live migration isn't the best approach (takes
> twice the memory and quite some time), but it's less intrusive and works
> fine (given localhost migration stability...)

Is this really using localhost live migration to move a domain from one
NUMA node to another on the same host? Why isn't there a simpler way?

cheers
john

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