From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J27Hp-0004vX-M8 for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:44:45 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J27Hn-0004rB-Rk for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:44:45 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J27Hn-0004qx-N4 for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:44:43 -0500 Received: from mx1.redhat.com ([66.187.233.31]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J27Hn-0000Cr-BR for qemu-devel@nongnu.org; Tue, 11 Dec 2007 10:44:43 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.1) with ESMTP id lBBFigC2004007 for ; Tue, 11 Dec 2007 10:44:42 -0500 Received: from file.surrey.redhat.com (file.fab.redhat.com [10.33.63.6]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lBBFif78018943 for ; Tue, 11 Dec 2007 10:44:42 -0500 Received: (from berrange@localhost) by file.surrey.redhat.com (8.13.1/8.13.1/Submit) id lBBFif9S006122 for qemu-devel@nongnu.org; Tue, 11 Dec 2007 15:44:41 GMT Date: Tue, 11 Dec 2007 15:44:41 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] [RFC] QEMU Dbus support - a proposal management API Message-ID: <20071211154441.GH17368@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: "Daniel P. Berrange" , 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 On Tue, Dec 11, 2007 at 09:16:43AM +0200, Yuval Kashtan wrote: > - This is very useful when you want to manage and control QEMU, for instance > developing a GUI to attach and detach usb devices or controlling more than > one instance of QEMU from a single management point, receiving parameters > externally and more. This capability is already possible using the monitor API. I've implemented it in libvirt, and in virt-manager and can easily hotplug/remove USB devices. So DBus is not required to do this and does not really make it any easier to use. DBus is very verbose to use from languages like C, so switching from the monitor to DBus API would not really help simplify my existing code. On the other hand, having a library providing a simple client side C API to send & receive monitor commands, would be beneficial Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|