From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56707 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OCqL1-0007oI-DY for qemu-devel@nongnu.org; Fri, 14 May 2010 04:33:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OCqKz-00038g-Cl for qemu-devel@nongnu.org; Fri, 14 May 2010 04:33:43 -0400 Received: from mx1.redhat.com ([209.132.183.28]:15590) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OCqKz-00038R-5V for qemu-devel@nongnu.org; Fri, 14 May 2010 04:33:41 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o4E8XdKh029646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 14 May 2010 04:33:39 -0400 From: Markus Armbruster Subject: Re: [Qemu-devel] [PATCH 1/2] QMP: Introduce commands doc References: <1273086712-29163-1-git-send-email-lcapitulino@redhat.com> <1273086712-29163-2-git-send-email-lcapitulino@redhat.com> <4BEC031D.6020506@redhat.com> <20100513115524.29f826a0@redhat.com> <20100513150136.GL12207@redhat.com> <4BEC276F.1020103@redhat.com> <20100513185748.7bcaf32c@redhat.com> Date: Fri, 14 May 2010 10:33:37 +0200 In-Reply-To: <20100513185748.7bcaf32c@redhat.com> (Luiz Capitulino's message of "Thu, 13 May 2010 18:57:48 -0300") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: bazulay@redhat.com, juzhang@redhat.com, Avi Kivity , qemu-devel@nongnu.org Luiz Capitulino writes: > On Thu, 13 May 2010 19:23:11 +0300 > Avi Kivity wrote: > >> On 05/13/2010 06:01 PM, Daniel P. Berrange wrote: >> > >> >> Yes, we do and it's used by libvirt iirc. >> >> >> > This command has been in QEMU for quite a long time now (0.9.x IIRC). >> > >> >> It wasn't in QMP until 0.12. We shouldn't have put it there in that form. > > Your main concern is stability? QMP in 0.12 and current are in preview > mode, ie. no stability contract until 0.13. And we absolutely need to make use of that license to improve stuff. Premature stability leads to stable crap. Having to get everything right the first time is just too hard for mortals. > We broke it already with a few changes (like capabilities support), so > anyone using QMP in 0.12 will have to update, although I don't think QMP > in 0.12 is that useful. > > Having said that, it's been stable for several weeks now and incompatible > changes have to be coordinated with libvirt. Yes, we should do our best not to break libvirt, and to help them out when we have to break it. That said, QMP is our chance to create a decent management interface. We really shouldn't drag in crap from the human monitor carelessly. > So, if you think this is worth the trouble someone could do it. > > PS: I remember Anthony saying that he'd put somewhere that QMP is a > preview version in 0.12. But I did not find anything, will submit > a patch for stable. I believe 0.12's QMP is too incomplete for serious use, so the risk of somebody investing big into 0.12's QMP only to get blindsided by 0.13's should be really low.