From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:42892)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1Uftoa-0003zk-Mt
	for qemu-devel@nongnu.org; Fri, 24 May 2013 11:21:59 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1UftoZ-0005gp-Dm
	for qemu-devel@nongnu.org; Fri, 24 May 2013 11:21:56 -0400
Date: Fri, 24 May 2013 11:21:52 -0400
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20130524112152.32ce478a@redhat.com>
In-Reply-To: <F0F196E9-1DAB-4542-B542-69EE3878F8DA@profihost.ag>
References: <519EFFA9.3070100@profihost.ag>
	<20130524092356.2f16521d@redhat.com>
	<94065BAF-4476-4709-A494-37E4A43884D3@profihost.ag>
	<20130524100242.39ec0b73@redhat.com>
	<F0F196E9-1DAB-4542-B542-69EE3878F8DA@profihost.ag>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] qmp commands get rejected
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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.