From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J27WZ-0007Hj-I3 for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:59:59 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J27WY-0007Gm-Nl for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:59:59 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J27WY-0007GR-GH for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:59:58 -0500 Received: from il.qumranet.com ([82.166.9.18]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J27WX-0002dB-Ti for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:59:58 -0500 Message-ID: <475EB3FC.1010106@qumranet.com> Date: Tue, 11 Dec 2007 17:59:56 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC] QEMU Dbus support - a proposal management API References: <475E5403.2000705@bellard.org> <1197364997.4242.10.camel@frecb07144> <475E617D.6090702@qumranet.com> <475EA3F4.50802@codemonkey.ws> <20071211150033.GC17368@redhat.com> <475EAE8F.4020209@codemonkey.ws> In-Reply-To: <475EAE8F.4020209@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Anthony Liguori wrote: > Yuval Kashtan wrote: >> As I can see, >> There is HUGH interest in management API for QEMU. >> seemly, DBus is NOT the right solution for direct integration into >> QEMU as it is not cross platform enough, pose extra dependency and >> (probably) not suitable for embedded systems. >> >> Keeping only the "old" monitor interface with no formal interface >> will make QEMU harder to integrate with as it requires extra work > > Why can't we make the monitor interface a "formal" interface? > Because then fixing a type or extending the interface becomes a pain. It's also much more difficult to specify a text-base interface completey, compared to a C api (where sometimes all you need is the header and a few comments). -- error compiling committee.c: too many arguments to function