From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42326) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbBxY-0001UI-QB for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:07:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RbBxP-0004i4-2s for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:06:56 -0500 Received: from mail-gx0-f173.google.com ([209.85.161.173]:57243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbBxO-0004hj-Sg for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:06:46 -0500 Received: by ggnk1 with SMTP id k1so2009483ggn.4 for ; Thu, 15 Dec 2011 06:06:45 -0800 (PST) Message-ID: <4EE9FEF1.4080709@codemonkey.ws> Date: Thu, 15 Dec 2011 08:06:41 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <20111215115731.3ee45e4b@doriath> In-Reply-To: <20111215115731.3ee45e4b@doriath> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Transitioning from HMP to QMP for QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: Kevin Wolf , Stefan Hajnoczi , qemu-devel , libvir-list@redhat.com, Adam Litke On 12/15/2011 07:57 AM, Luiz Capitulino wrote: > On Thu, 15 Dec 2011 13:02:40 +0000 > Stefan Hajnoczi wrote: > >> What is the status of QEMU's transition from HMP to the QMP interface? > > Depends on what you consider the transition to be. > > For management tools the transition can be considered done already because we > do not support HMP as a stable interface. > >> My current understanding is that QEMU provides new HMP commands for >> humans, but HMP is being phased out as an API. > > It already did. > >> 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. > > Exactly. > >> 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. > > Maybe it's a matter of terminology, but I have the impression you're > talking about two things here: > > 1. HMP will always exist, in the meaning that qemu will always provide > a human interface. If we move it to a python script or some kind of > external process, that's an implementation detail. > > This means that, if you're adding new functionality to qemu and it > does make sense for humans to use it, then it should have a HMP > version. > > 2. If you do add the HMP interface, that's for humans to consume and > its output/semantics should make sense for humans, not for management tools. 3. All HMP commands will be implemented in terms of QMP commands (and only in terms of QMP commands). There are still a lot of HMP commands that don't have an QMP analog. Luiz, it might make sense to setup a wiki page which instructions on how to convert an HMP command to a QMP command using QAPI. If we did that, we could probably get more folks involved in the conversion process. Regards, Anthony Liguori > >> 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. >> >> Stefan >> > >