From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N92G8-0005g8-MD for qemu-devel@nongnu.org; Fri, 13 Nov 2009 14:56:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N92G3-0005fO-Nn for qemu-devel@nongnu.org; Fri, 13 Nov 2009 14:56:39 -0500 Received: from [199.232.76.173] (port=44357 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N92G3-0005fL-Hs for qemu-devel@nongnu.org; Fri, 13 Nov 2009 14:56:35 -0500 Received: from mx1.redhat.com ([209.132.183.28]:11856) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N92G2-0004pk-Re for qemu-devel@nongnu.org; Fri, 13 Nov 2009 14:56:35 -0500 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id nADJuXSl023965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 13 Nov 2009 14:56:33 -0500 Received: from doriath (vpn-10-251.rdu.redhat.com [10.11.10.251]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id nADJuOiR018905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 13 Nov 2009 14:56:32 -0500 Date: Fri, 13 Nov 2009 17:56:15 -0200 From: Luiz Capitulino Message-ID: <20091113175615.4c9fea15@doriath> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] QMP unstable tree status List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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