From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LNYoB-0000HH-Cp
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 15:27:19 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LNYoA-0000FT-82
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 15:27:18 -0500
Received: from [199.232.76.173] (port=38845 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LNYo9-0000Ey-Nn
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 15:27:17 -0500
Received: from mail-qy0-f20.google.com ([209.85.221.20]:58474)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1LNYo9-0006p5-CT
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 15:27:17 -0500
Received: by qyk13 with SMTP id 13so1909480qyk.10
	for <qemu-devel@nongnu.org>; Thu, 15 Jan 2009 12:27:16 -0800 (PST)
Message-ID: <496F9C19.8020502@codemonkey.ws>
Date: Thu, 15 Jan 2009 14:27:05 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Machine-readable or parseable qemu output
References: <20090114111005.GB31839@amit-x200.pnq.redhat.com>
	<20090114112317.GD24995@redhat.com>
In-Reply-To: <20090114112317.GD24995@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
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: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Amit Shah <amit.shah@redhat.com>, chrisw@redhat.com, dlaor@redhat.com, avi@redhat.com, rjones@redhat.com

Daniel P. Berrange wrote:
> On Wed, Jan 14, 2009 at 04:40:05PM +0530, Amit Shah wrote:
>   
>> Hello,
>>
>> Continuing from the thread at [1], building on Daniel's suggestions, I
>> have jot down a few points as to how a libqemumonitor API could be
>> developed.
>>
>> To recap, there has to be an interface to the qemu monitor in
>> a way that wouldn't break even if the monitor output changes. This API
>> will remain the same, so that consumers (libvirt, etc) can safely
>> integrate with the monitor.
>>
>> Please see Dan's email at [1] to get the background details.
>>
>> [1] http://www.mail-archive.com/qemu-devel@nongnu.org/msg14615.html
>>
>> Here are some initial thoughts. Comments?
>>     
>
> I'd like to add one more requirement
>
>  - Works with existing QEMU monitor for releases >= 0.8.0
>   

I think this is a bad requirement.

> This is because libvirt currently supports all QEMU >= 0.8.0,

libvirt has no bearing on upstream QEMU support :-)

>  so if
> we're to be able to make use of this library we can't restrict it
> to just new releases.

But you can conditionally use the new library instead of your custom 
parsing code for newer QEMU versions.

Regards,

Anthony Liguori