From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L113b-00070Z-Hx
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 10:58:03 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L113Y-00070L-Ga
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 10:58:03 -0500
Received: from [199.232.76.173] (port=60668 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L113Y-00070I-B1
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 10:58:00 -0500
Received: from mx2.redhat.com ([66.187.237.31]:47973)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <markmc@redhat.com>) id 1L113X-0006k8-Fd
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 10:58:00 -0500
Subject: Re: [Qemu-devel] Re: [PATCH 0/5] Add "info capabilities" monitor
	command
From: Mark McLoughlin <markmc@redhat.com>
In-Reply-To: <20081114035122.GM2055@shareable.org>
References: <1226594763-2304-1-git-send-email-markmc@redhat.com>
	<491CF04F.5020408@codemonkey.ws> <20081114035122.GM2055@shareable.org>
Content-Type: text/plain
Date: Fri, 14 Nov 2008 15:56:49 +0000
Message-Id: <1226678209.9332.92.camel@blaa>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: Mark McLoughlin <markmc@redhat.com>, 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: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org

On Fri, 2008-11-14 at 03:51 +0000, Jamie Lokier wrote:

> If it's "wrong" the first time, well, there are other features in QEMU
> which have changed incompatibly between versions.  Imho, there's no
> great harm in changing "info capability" output until it's right,
> provided the basic syntax unambiguously represents the QEMU version
> and capability text format version somehow.

Well, the goal here is to have something actually usable by management
tools and an in-flux format wouldn't help that.

But yeah, we should agree on enough of the basic details of the format
to allow a format version to be exposed.

> While we're at it, a section describing the monitor's capabilities so
> we don't have to parse the _monitor's_ "help" output....  Oh, there I
> go bike-shedding again :-)

Well, if "info capabilities" isn't implemented, simply having it fail is
fine.

That's a bit different from e.g. libvirt launching qemu with
cache=writethrough, detecting that qemu doesn't support that and
relaunching without it.

Cheers,
Mark.