From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J22vq-0006DY-2S for qemu-devel@nongnu.org; Tue, 11 Dec 2007 06:05:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J22vo-0006BB-6R for qemu-devel@nongnu.org; Tue, 11 Dec 2007 06:05:45 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J22vn-0006Az-W1 for qemu-devel@nongnu.org; Tue, 11 Dec 2007 06:05:44 -0500 Received: from il.qumranet.com ([82.166.9.18]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J22vn-0000ZC-Hf for qemu-devel@nongnu.org; Tue, 11 Dec 2007 06:05:43 -0500 Message-ID: <475E6F02.9000302@qumranet.com> Date: Tue, 11 Dec 2007 13:05:38 +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> In-Reply-To: <475E5403.2000705@bellard.org> 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 Fabrice Bellard wrote: > Hi, > > At this point I am not interested in integrating it into QEMU as it is > one more API level to maintain in addition to the command line > monitor. However, I can change my mind if several projects insists to > have a similar interface. > I think that many projects now want to control qemu programatically. The monitor is not a good interface since it is text-based, hard to parse, and liable to change without notice when new features are added. However, I agree that having many similar constructs is not a good thing, and that we should retain the monitor for non-programmatic control. What do you say to implementing the qemu interface as a plugin API, and implementing the monitor on top of this API? e.g.: qemu loads /usr/local/lib/qemu/libmonitor.so, which uses the API to export the good old qemu monitor interface. If it finds /usr/local/lib/qemu/libdbus.so, it loads an additional dbus interface. If libvirt wants to drop a libvirtapi.so into that directory, it can control qemu through that. -- error compiling committee.c: too many arguments to function