From: Luiz Capitulino <lcapitulino@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Dietmar Maurer <dietmar@proxmox.com>,
"qemu-stable@nongnu.org" <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] qmp commands get rejected
Date: Fri, 24 May 2013 11:21:52 -0400 [thread overview]
Message-ID: <20130524112152.32ce478a@redhat.com> (raw)
In-Reply-To: <F0F196E9-1DAB-4542-B542-69EE3878F8DA@profihost.ag>
On Fri, 24 May 2013 16:36:26 +0200
Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
> Am 24.05.2013 um 16:02 schrieb Luiz Capitulino <lcapitulino@redhat.com>:
>
> > On Fri, 24 May 2013 15:57:59 +0200
> > Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
> >
> >> Am 24.05.2013 um 15:23 schrieb Luiz Capitulino <lcapitulino@redhat.com>:
> >>
> >>> On Fri, 24 May 2013 07:50:33 +0200
> >>> Stefan Priebe <s.priebe@profihost.ag> wrote:
> >>>
> >>>> Hello list,
> >>>>
> >>>> since upgrading from qemu 1.4.1 to 1.5.0 i've problems with qmp commands.
> >>>>
> >>>> With Qemu 1.5 i've the following socket communication:
> >>>>
> >>>> '{"execute":"qmp_capabilities","id":"12125:1","arguments":{}}'
> >>>>
> >>>> '{"return": {}, "id": "12125:1"}'
> >>>>
> >>>> '{"execute":"qom-set","id":"12125:2","arguments":{"value":2,"path":"machine/peripheral/balloon0","property":"guest-stats-polling-interval"}}'
> >>>>
> >>>> '{"QMP": {"version": {"qemu": {"micro": 0, "minor": 5, "major": 1},
> >>>> "package": ""}, "capabilities": []}}'
> >>>>
> >>>> '{"id": "12125:2", "error": {"class": "CommandNotFound", "desc": "The
> >>>> command qom-set has not been found"}}'
> >>>>
> >>>>
> >>>> It seems that the command mode (qmp_capabilities) gets resets by the
> >>>> welcome banner?
> >>>
> >>> It looks like you got disconnected before qom-set was issued.
> >>
> >> No its the same socket connection. No disconnect had happened.
> >>
> >>>
> >>> Can you share more details on how those commands are being issued?
> >>
> >> They're send through socket with a perl script. What do you need?
> >
> > That perl script maybe? I can't reproduce the problem.
>
> I would try to create a small example script.
I use qmp-shell and other little scripts very often.
> Am this be due to the fact that I don't wait for the welcome banner right now?
If you're not reading from the socket, then you'll get the banner back when
you read your first response. But qom-set shouldn't fail because of that.
next prev parent reply other threads:[~2013-05-24 15:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 5:50 [Qemu-devel] qmp commands get rejected Stefan Priebe
2013-05-24 13:23 ` Luiz Capitulino
2013-05-24 13:57 ` Stefan Priebe - Profihost AG
2013-05-24 14:02 ` Luiz Capitulino
2013-05-24 14:36 ` Stefan Priebe - Profihost AG
2013-05-24 15:21 ` Luiz Capitulino [this message]
2013-05-24 20:12 ` Stefan Priebe
2013-05-24 21:37 ` Stefan Priebe
2013-05-24 22:03 ` Stefan Priebe
2013-05-24 22:04 ` Stefan Priebe
2013-05-24 22:09 ` [Qemu-devel] [Qemu-stable] " mdroth
2013-05-24 22:12 ` Stefan Priebe
2013-05-24 22:32 ` mdroth
2013-05-25 11:09 ` Stefan Priebe
2013-05-26 1:23 ` mdroth
2013-05-26 15:13 ` Stefan Priebe
2013-05-26 15:36 ` mdroth
2013-05-26 20:52 ` Stefan Priebe
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=20130524112152.32ce478a@redhat.com \
--to=lcapitulino@redhat.com \
--cc=dietmar@proxmox.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=s.priebe@profihost.ag \
/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).