From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Przywara Subject: future plans for libxl? Date: Wed, 14 Apr 2010 10:12:15 +0200 Message-ID: <4BC578DF.9000508@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Hi, what is the current master plan for libxl? Currently I see that many features already implemented in Python are again implemented in libxl (migration, CPU affinity). Are the Python tools going to be replaced at some point in the future or are they just reimplemented to be based upon libxl? For the NUMA guest effort I would like to get some ideas on how to handle tool chain implementation. Or is it intended to have both these implementations in parallel (which would be kind of unfortunate)? And how does this affect xend? I see that in opposite to xm some functionality of the xl tool works without having xend running (which I find very handy, cause I spent countless hours during development to just fix some weird xend issues just for calling xm info or xm vcpu-list). Was there a mail or a document I missed already explaining this? Thanks! Andre. -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 448 3567 12 ----to satisfy European Law for business letters: Advanced Micro Devices GmbH Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632