RE: [Xen-devel] future plans for libxl?

["Xu, Jiajun" <jiajun.xu@xxxxxxxxx>]

Is there any example config file we can follow to create guest with 'xl'? If 
there is a reference doc or readme, it would be much convenient for user.
And seems following functions are not supported in 'xl' yet: HAP option, 
PCI-Passthrough-Strict-Check like ACS capability check, HVM S3 resume support 
by 'xm trigger' and function like 'xm info'.

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefano
> Stabellini
> Sent: Wednesday, April 14, 2010 11:49 PM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Ian Jackson
> Subject: Re: [Xen-devel] future plans for libxl?
> 
> On Wed, 14 Apr 2010, Andre Przywara wrote:
> > 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?
> >
> 
> You didn't miss any email, we were planning on talking about this at
> the next XenSummit.
> 
> Libxenlight is almost feature complete already: there are few things
> missing, but not much.
> Implementing the missing features and making the library rock solid are
> our top priorities and we hope to get them done by the 4.1 release.
> We also want to port xend and XCP to libxenlight to remove code
> duplication and make it easier for xen and kernel developers to add new
> features to the toolstacks.
> The xl tool is going to be the main testing tool for libxenlight and is
> going to provide a command line interface 99% compatible with xm; once
> libxenlight is complete and robust we would like people that currently
> use xend, especially developers, to try out xl.
> Even though xend will be ported to libxenlight, xl is going to be
> smaller and well tested, therefore we encourage people that don't need
> advanced xend features, like managed domains or the XML RPC interface,
> to use xl.

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