From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:37960) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QZlBO-00037E-Gg for qemu-devel@nongnu.org; Thu, 23 Jun 2011 10:47:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QZlBM-00006L-TV for qemu-devel@nongnu.org; Thu, 23 Jun 2011 10:47:02 -0400 Received: from e38.co.us.ibm.com ([32.97.110.159]:35618) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QZlBM-000066-CH for qemu-devel@nongnu.org; Thu, 23 Jun 2011 10:47:00 -0400 Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p5NEcQSv013191 for ; Thu, 23 Jun 2011 08:38:26 -0600 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p5NEkXjO235436 for ; Thu, 23 Jun 2011 08:46:34 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p5NEkTks010353 for ; Thu, 23 Jun 2011 08:46:29 -0600 Message-ID: <4E0351C3.7030704@linux.vnet.ibm.com> Date: Thu, 23 Jun 2011 09:46:27 -0500 From: Michael Roth MIME-Version: 1.0 References: <4E023A9D.9010205@linux.vnet.ibm.com> <20110623092954.GA2682@bow.redhat.com> <20110623113835.GC14307@redhat.com> In-Reply-To: <20110623113835.GC14307@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] RFC: Qemu Guest Tools ISO List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: agl@linux.vnet.ibm.com, Stefan Hajnoczi , "qemu-devel@nongnu.org Developers" , Anthony Liguori , pmyers@redhat.com, bsarathy@redhat.com On 06/23/2011 06:38 AM, Daniel P. Berrange wrote: > On Thu, Jun 23, 2011 at 12:08:26PM +0100, Stefan Hajnoczi wrote: >> On Thu, Jun 23, 2011 at 10:29 AM, Alon Levy wrote: >>> On Wed, Jun 22, 2011 at 01:55:25PM -0500, Michael Roth wrote: >>>> Goal: >>>> >>>> Provide a mechanism, similar to vmware and virtualbox guest tools >>>> ISOs, that allows us to easily distribute guest tools (and >>>> potentially drivers) for linux and windows guests. >>> >>> What would be the advantage for linux guests, with their package managers already >>> handling this task? I see how it would make testing easier with various linux >>> distributions, but for management I wonder if it won't be easier to use the >>> package management system to update the guests same as the hosts. >> >> If the guest tools come from the host QEMU we don't need complicated >> compatibility testing and fallbacks. Guest and host will be in sync >> and support the same features. >> >> I'm not sure how we can update guest tools when the QEMU on the host >> is updated though. > > While an ISO is a good option for the initial deployment, since it can > be used to provide both the virtio drivers + agents together, once you > have the virtio stuff installed in the guest, it might be worth exposing > updated tools via a 9p filesystem mount. For Linux guest the 9p fs > exposed could include a YUM repo (or equiv) which the guest update tool > would automatically see and pull updates from, since 9pfs is "live" > unlike an ISO. > > Regards, > Daniel Definitely, or at least some form of automating the install beyond the initial one. One approach would be extending the guest RPC agent that would ship with the ISO to be able to kick off a future update. Implementing in would be pretty simple too: Guest agent: add RPC will execute the ISO installer QMP: add command that will mount latest ISO as a cdrom then initiate the update via the guest agent RPC. We could even take the ISO out of the equation after the initial install, since files can be pushed to the guest via guest agent/virtio-serial