Hi, the following patch adds NUMA node migration based on live migration to xend. By adding another parameter to "xm migrate" the target NUMA node number gets propagated to the target host (can be both localhost or a remote host). The restore function then sets the VCPU affinity 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...) Feedback appreciated, especially since I speak Python since Monday... 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@lists.xensource.com http://lists.xensource.com/xen-devel