From: Stefan Hajnoczi <stefanha@gmail.com>
To: libvir-list@redhat.com, qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Adam Litke <agl@us.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] Transitioning from HMP to QMP for QEMU
Date: Thu, 15 Dec 2011 13:02:40 +0000 [thread overview]
Message-ID: <CAJSP0QWT0m3ZfaPvOXXv+gpu89c-BioayQruNy0Jh1K5LokSxw@mail.gmail.com> (raw)
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.
Stefan
next reply other threads:[~2011-12-15 13:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 13:02 Stefan Hajnoczi [this message]
2011-12-15 13:18 ` [Qemu-devel] Transitioning from HMP to QMP for QEMU Jan Kiszka
2011-12-15 13:33 ` Kevin Wolf
2011-12-15 13:37 ` Jan Kiszka
2011-12-15 13:38 ` Lucas Meneghel Rodrigues
2011-12-15 13:39 ` Jan Kiszka
2011-12-15 13:45 ` Stefan Hajnoczi
2011-12-15 13:49 ` Kevin Wolf
2011-12-15 13:53 ` Stefan Hajnoczi
2011-12-15 13:57 ` Jan Kiszka
2011-12-15 15:01 ` Luiz Capitulino
2011-12-15 13:31 ` [Qemu-devel] [libvirt] " Stefan Berger
2011-12-15 13:57 ` [Qemu-devel] " Luiz Capitulino
2011-12-15 14:06 ` Anthony Liguori
2011-12-15 14:52 ` Luiz Capitulino
2011-12-15 14:57 ` Anthony Liguori
2011-12-15 14:23 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJSP0QWT0m3ZfaPvOXXv+gpu89c-BioayQruNy0Jh1K5LokSxw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=agl@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).