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] (resent) NUMA node migration

To: "John Levon" <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] (resent) NUMA node migration
From: "Andre Przywara" <andre.przywara@xxxxxxx>
Date: Wed, 09 Jan 2008 15:35:49 +0100
Cc: Ian.Pratt@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Jan 2008 06:43:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071222005315.GA11052@xxxxxxxxxxxxxxxxxxxxxxx>
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> <20071222005315.GA11052@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (X11/20070409)
John Levon wrote:
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),
After thinking more about this, I came to the conclusion that this is not entirely true. If you want to transfer the guest from one node (with it's own memory) to another node (with it's own memory), then you would need to have this amount of memory available at the target anyway. The performance problem can maybe overcome by not using TCP/IP to loopback, but a more direct solution (or by reverting to a UNIX socket).

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?
Well, Ian described the "simpler way" (thanks for that), I would call it more elegant and efficient, but simpler is not the word that comes to mind... One advantage of this solution is that the guest stays the same and there is no interruption. Also one could think about migrating hot pages first and letting the rest be done in the background more slowly (this is how VMware does this).


Regards,
Andre.

--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy



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

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] [PATCH] (resent) NUMA node migration, Andre Przywara <=