Re: [Xen-devel] [PATCH] Fix pci passthru in xend interface used by libvirt [and 1 more messages]

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Mon, 8 Nov 2010, Jim Fehlig wrote:
> Ian Jackson wrote:
> > Jim Fehlig writes ("[Xen-devel] [PATCH] Fix pci passthru in xend interface 
> > used by libvirt"):
> >   
> >> Attempting to define or create a domain whose XML config contains a
> >> passthru PCI device fails with libvirt
> >>     
> >
> > Thanks for this report.  I'm afraid that no-one any more seems to know
> > much about the protocol that libvirt speaks to xend.  And, xend is on
> > the way out - we're trying to push the new libxl library instead.
> >   
> 
> Heh, I was just beginning to craft a mail asking for some clarity on
> "xend is on the way out".  I've seen comments on the list about
> deprecating xend and switching to the new tool stack, but can't seem to
> find any details about the change.  I have seen Stefano's talk on
> libxenlight from spring Xen Summit, which states xend will be 'ported'
> to libxenlight.  But as you hint, I don't think this is the case - and
> it sounds like a rather unpleasant task :-).
> 

Porting xend to libxenlight is certainly an unpleasant task, however it
would smooth the overall transition to libxenlight.
In the last few months the adoption of xl/libxenlight has exceeded our
expectations so porting xend to libxenlight may be unnecessary and
perhaps the engineering resources would be better spent in porting
libvirt to libxenlight sooner.


> > So it would be worth thinking about changing libvirt to use libxl
> > instead.
> >   
> 
> Yes, I thought about it while investigating this bug.  I think some
> answers to my questions above will help prioritize this task.
> 

Libvirt should be ported to libxenlight because libxenlight is going to
be the default toolstack of the xen 4.1 release and having libvirt
talking to libxenlight directly is certainly the right architectural
choice.
We are keen on having multiple libxenlight users and we would provide
all the help necessary to accomplish this task.


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