From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33180 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P8uml-0002A2-B6 for qemu-devel@nongnu.org; Thu, 21 Oct 2010 09:02:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P8umk-0007nx-2f for qemu-devel@nongnu.org; Thu, 21 Oct 2010 09:02:23 -0400 Received: from mail-qw0-f45.google.com ([209.85.216.45]:46925) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P8umk-0007nt-0X for qemu-devel@nongnu.org; Thu, 21 Oct 2010 09:02:22 -0400 Received: by qwh5 with SMTP id 5so3677078qwh.4 for ; Thu, 21 Oct 2010 06:02:21 -0700 (PDT) Message-ID: <4CC039DA.5090607@codemonkey.ws> Date: Thu, 21 Oct 2010 08:02:18 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] KVM call minutes for Oct 19 References: <20101019151441.GA24673@x200.localdomain> <4DE00079-05FA-40DF-9EA5-9573AD745117@suse.de> <4CBEE84F.7060207@codemonkey.ws> <20101020131925.GH15143@redhat.com> <4CBEECE6.8030605@codemonkey.ws> <4CBF7154.2070304@redhat.com> <9DABD2D4-389E-4D05-8A4C-2DE1E20D3B5C@suse.de> <4CBFEF95.9060703@redhat.com> In-Reply-To: <4CBFEF95.9060703@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Chris Wright , "kvm@vger.kernel.org" , "dlaor@redhat.com" , Alexander Graf , "qemu-devel@nongnu.org" On 10/21/2010 02:45 AM, Paolo Bonzini wrote: > On 10/21/2010 03:14 AM, Alexander Graf wrote: >>> I agree that some agent code for basic stuff like live snapshot >>> sync with the filesystem is small enough and worth to host within >>> qemu. Maybe we do need more than one project? >> >> No, please. That's exactly what I don't want to see. The >> libvirt/qemu/virt-man split is killing us already. How is this going >> to become with 20 driver packs for the guest? > > Agreed. Not relying on Mata Hari and reinventing a dbus/WMI interface > would be yet another case of QEMU NIH. I think we're about 10 steps ahead of where we should be right now. The first step is just identifying what interfaces we need in a guest agent. So far, I think we can get away with a very small number of interfaces (mainly read/write files, execute command). > The same argument also works on the backend BTW, it can be virtio > serial but also a Xen pvconsole and that wheel should not be > reinvented either. > > The guest agent should be a pluggable architecture, and QEMU can > provide plugins for sync, spice, "info balloon" and everything else it > needs. virtio-serial is essentially our plugin interface. The core QEMU agent would use org.qemu.guest-agent and a spice against could use org.spice-space.guest-agent. The QEMU agent should have an interface that terminates in QEMU itself. Regards, Anthony Liguori > Paolo