From: Eric Blake <eblake@redhat.com>
To: Erik Rull <erik.rull@rdsoftware.de>, paulo.vital@profitbricks.com
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Getting VM state from outside QEMU?
Date: Wed, 08 Apr 2015 10:34:21 -0600 [thread overview]
Message-ID: <5525588D.3000503@redhat.com> (raw)
In-Reply-To: <1564966247.40468.1428510084034.JavaMail.open-xchange@oxbaltgw07.schlund.de>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On 04/08/2015 10:21 AM, Erik Rull wrote:
>>> 172.17.48.45 ~ # telnet 127.0.0.1 4444
>>> {"QMP": {"version": {"qemu": {"micro": 0, "minor": 1, "major": 2},
>>> "package":
>>> ""}, "capabilities": []}}
>>
>> You HAVE to use {"execute":"qmp_capabilities"} (possibly with an
>> "id":...) as your first command on the monitor, before you can issue any
>> other command. I really wish we could improve the error message:
> Thanks! That fixed it - even if I don't know why this was actually necessary :-)
docs/qmp/qmp-spec.txt
It's part of the protocol, to allow us to make non-backwards-compatible
changes to how QMP is parsed while still keeping sane interactions
between mismatches in server vs. client (to date, we have wisely not
needed to add any capabilities).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-04-08 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 13:31 [Qemu-devel] Getting VM state from outside QEMU? Erik Rull
2015-04-07 13:42 ` Paulo Ricardo Paz Vital
2015-04-08 16:10 ` Erik Rull
2015-04-08 16:16 ` Eric Blake
2015-04-08 16:21 ` Erik Rull
2015-04-08 16:34 ` Eric Blake [this message]
2015-04-09 7:33 ` Paulo Ricardo Paz Vital
2015-04-07 18:16 ` John Snow
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=5525588D.3000503@redhat.com \
--to=eblake@redhat.com \
--cc=erik.rull@rdsoftware.de \
--cc=paulo.vital@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.