From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Nud2Q-0000P9-WA
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 22:43:15 -0400
Received: from [140.186.70.92] (port=33525 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Nud2O-0000P1-Pa
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 22:43:13 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1Nud2N-0002Pv-Ji
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 22:43:12 -0400
Received: from mail2.shareable.org ([80.68.89.115]:46240)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1Nud2N-0002Pp-Cg
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 22:43:11 -0400
Date: Thu, 25 Mar 2010 02:43:02 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in
	libvirt
Message-ID: <20100325024302.GB28176@shareable.org>
References: <4BA7C40C.2040505@codemonkey.ws> <4BA962F3.1020107@codemonkey.ws>
	<m3wrx2c9wz.fsf@blackfin.pond.sub.org>
	<201003241225.30442.paul@codesourcery.com>
	<4BAA0A1E.2080805@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BAA0A1E.2080805@codemonkey.ws>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>, Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>, Alexander Graf <agraf@suse.de>

Anthony Liguori wrote:
> But the advantage is that if libvirt provided an API for a QMP transport 
> encapsulated in their secure protocol, then provided the plumbed that 
> API through their Python interface, you could use it for free in Python 
> without having to reinvent the wheel.

It's not free if the only "free" way to access all qemu's capabilities
from Python requires you to switch all your config files to libvirt's
format and libvirt's way of doing things. There's quite a big jump
from the qemu/kvm way of doing things and the libvirt way, and the
latter isn't well matched to all uses of qemu.

But if libvirt exposes the same QMP as direct to qemu, or something
very similar (it could wrap it, and add it's own libvirt events,
commands and properties), that would be great for scripts that could
then work with either with minimal change.

-- Jamie