qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QMP unstable tree status
Date: Fri, 13 Nov 2009 17:56:15 -0200	[thread overview]
Message-ID: <20091113175615.4c9fea15@doriath> (raw)


 Hi there,

 I've updated my QMP patches to work on top of Anthony's QJSON and my
conversion series.

 I was planning to post them as an RFC today, but turns out that there are
issues to be fixed and some cleanup to be done.

 Anyway, it's already in the master branch of my qmp-unstable tree:

http://repo.or.cz/w/qemu/qmp-unstable.git

 The most annoying issue is the lack of error handling, I've added some
simple checks but currently it isn't possible to know what went wrong.

 Here goes an example of a simple session:

"""
$ qemu [...] -monitor control,tcp:localhost:4444,server

[...]

$ telnet localhost 4444
Trying ::1...
Connected to localhost.
Escape character is '^]'.
{ "QMP": { "capabilities": [] } }
{ "execute": "info", "id": 42, "arguments": { "item": "version" } }
{"timestamp": "", "return": "0.11.50", "id": 42}
"""

 The QMP wiki page contains up to date information about the
conversion work:

http://www.linux-kvm.org/page/MonitorProtocol

                 reply	other threads:[~2009-11-13 19:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20091113175615.4c9fea15@doriath \
    --to=lcapitulino@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).