From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Veillard Subject: Re: Libvir: a simple C virtualization control library Date: Thu, 15 Dec 2005 12:54:54 -0500 Message-ID: <20051215175454.GR23448@redhat.com> References: <20051215150327.GL23448@redhat.com> <200512151126.12652.hollisb@us.ibm.com> Reply-To: veillard@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <200512151126.12652.hollisb@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Hollis Blanchard Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Dec 15, 2005 at 11:26:12AM -0600, Hollis Blanchard wrote: > On Thursday 15 December 2005 09:03, Daniel Veillard wrote: > > =A0The libvir library is born from the need for a simpler userland C = library > > to watch and control Xen domains. >=20 > I'm curious why libxc isn't good enough. Is the emphasis here on "simpl= er"?=20 > >From what I've seen of it so far, I'm not sure I'd call libxc overly=20 > complicated... I would say simpler to use, I'm not really targetting the same kind of developpers I guess application and tools developpers not system programm= ers. To me libxc is very low level, the high level abstractions are available = on top of the python classes but not at the C level. Basically if you want t= o reuse Xen at the application level, you are pushed to Python + GPL which is not necessarily an easy spot to stay in. > The reason I'm interested is that right now the PPC port is carrying so= me=20 > libxc hacks for domain creation, which already have caused merge confli= cts.=20 > There's no pressing need for us to throw out our hacks at the moment, b= ut=20 > longer term if it's difficult for us to fit into libxc then maybe libvi= r=20 > would be a better fit. I don't think of libvir as a replacement for libxc, so a-priori I'm not= sure it really fits, especially as libvir has no domain creation API yet, but = the library will go where the user base will drive it. Daniel --=20 Daniel Veillard | Red Hat http://redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/