From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55011) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQMtE-0003zz-Ak for qemu-devel@nongnu.org; Tue, 15 Nov 2011 12:33:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQMt9-0005uR-Oj for qemu-devel@nongnu.org; Tue, 15 Nov 2011 12:33:44 -0500 Received: from mx1.redhat.com ([209.132.183.28]:13600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQMt9-0005uE-Hi for qemu-devel@nongnu.org; Tue, 15 Nov 2011 12:33:39 -0500 Date: Tue, 15 Nov 2011 19:33:31 +0200 From: Alon Levy Message-ID: <20111115173331.GS7140@garlic.redhat.com> References: <201111151924.41357.bazulay@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201111151924.41357.bazulay@redhat.com> Subject: Re: [Qemu-devel] converging around a single guest agent List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Barak Azulay Cc: Gal Hammer , arch@ovirt.org, qemu-devel@nongnu.org, vdsm-devel@lists.fedorahosted.org On Tue, Nov 15, 2011 at 07:24:40PM +0200, Barak Azulay wrote: > Hi, > > One of the breakout sessions during the ovirt workshop [1] was about the guest > tools, and focused mainly on the ovirt-guest-agent [2]. > > One of the issues discussed there, was the various existing guest agents out > there, and the need to converge the efforts to a single agent that will serve > all. > > while 4 agents were mentioned (Matahari, vdagent, qemu-ga & ovirt-guest-agent) > during that discussion, we narrowed it down to 2 candidates: > > qemu-ga (aka virt-agent): > ------------------------- > - Qemu specific - it was aimed for specific qemu needs (mainly quiesce guest > I/O) > - Communicates directly with qemu (not implemented yet) > - Supports ? > - So far linux only > - written in C > > Ovirt-guest-agent: > ------------------ > - Has been around for a long time (~5 years) - considered stable > - Started as rhevm specific but evolved a lot since then > - Currently the only fully functional guest agent available for ovirt > - Written in python > - Some VDI related sub components are written in C & C++ > - Supports a well defined list of message types / protocol [3] > - Supports the folowing guest OSs > Linux: RHEL5, RHEL6 F15, F16(soon) Does it have a seperate system level and user level part in Linux? It does in windows, right? This is a requirment for replacing vdagent+vdservice and the linux spice-agent, they both need to be active during login stage, and then launch a new session agent when the user is logged in. This is true for both linux and windows, although we have completely different code bases for them: http://cgit.freedesktop.org/spice/linux/vd_agent/ http://cgit.freedesktop.org/spice/win32/vd_agent/ linux is C, windows is C++ btw. > Windows: xp, 2k3 (32/64), w7 (32/64), 2k8 (32/64/R2) > > > The need to converge is obvious, and now that ovirt-guest-agent is opensourced > under the ovirt stack, and since it already produces value for enterprise > installations, and is cross platform, I offer to join hands around ovirt- > guest-agent and formalize a single code base that will serve us all. > > git @ git://gerrit.ovirt.org/ovirt-guest-agent > > Thoughts ? > > Thanks > Barak Azulay > > [1] http://www.ovirt.org/news-and-events/workshop > [2] http://www.ovirt.org/wiki/File:Ovirt-guest-agent.odp > [3] http://www.ovirt.org/wiki/Ovirt_guest_agent >