From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbBPy-0005BA-10 for qemu-devel@nongnu.org; Thu, 15 Dec 2011 08:32:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RbBPs-0004sY-9V for qemu-devel@nongnu.org; Thu, 15 Dec 2011 08:32:13 -0500 Received: from e38.co.us.ibm.com ([32.97.110.159]:42432) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbBPs-0004sO-4I for qemu-devel@nongnu.org; Thu, 15 Dec 2011 08:32:08 -0500 Received: from /spool/local by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 15 Dec 2011 06:32:05 -0700 Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pBFDVthQ128034 for ; Thu, 15 Dec 2011 06:31:57 -0700 Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pBFDVgZZ029946 for ; Thu, 15 Dec 2011 06:31:42 -0700 Message-ID: <4EE9F6BB.3020309@linux.vnet.ibm.com> Date: Thu, 15 Dec 2011 08:31:39 -0500 From: Stefan Berger MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [libvirt] Transitioning from HMP to QMP for QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: libvir-list@redhat.com, Kevin Wolf , Anthony Liguori , qemu-devel On 12/15/2011 08:02 AM, Stefan Hajnoczi wrote: > What is the status of QEMU's transition from HMP to the QMP interface? > > My current understanding is that QEMU provides new HMP commands for > humans, but HMP is being phased out as an API. Management tools > should rely only on QMP for new commands. That would mean new HMP > commands are not guaranteed to produce backwards-compatible output > because tools are not supposed to parse the output. > > On the libvirt side, new QEMU features should only be supported via > the json monitor in the future (i.e. human monitor patches should not > be sent/merged)? Existing HMP commands will still need the human > monitor support in order to handle old QEMU versions gracefully, but > I'm thinking about new commands only. > > Does everyone agree on this? I think this is an important discussion > if we want our management interface to get better and more consistent > in the future. > HMP is good for a human to interaction with Qemu, QMP mostly for a machine. At least that's my impression. If there are no new HMP commands hopefully there is an alternative for human interaction. Stefan