From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: agl@linux.vnet.ibm.com, Michael Roth <mdroth@linux.vnet.ibm.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
pmyers@redhat.com, bsarathy@redhat.com
Subject: Re: [Qemu-devel] RFC: Qemu Guest Tools ISO
Date: Thu, 23 Jun 2011 12:38:35 +0100 [thread overview]
Message-ID: <20110623113835.GC14307@redhat.com> (raw)
In-Reply-To: <BANLkTi=kGdSKueHGyndbqie1SHcJMUOtUw@mail.gmail.com>
On Thu, Jun 23, 2011 at 12:08:26PM +0100, Stefan Hajnoczi wrote:
> On Thu, Jun 23, 2011 at 10:29 AM, Alon Levy <alevy@redhat.com> 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
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2011-06-23 11:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 18:55 [Qemu-devel] RFC: Qemu Guest Tools ISO Michael Roth
2011-06-23 9:29 ` Alon Levy
2011-06-23 11:08 ` Stefan Hajnoczi
2011-06-23 11:38 ` Daniel P. Berrange [this message]
2011-06-23 14:46 ` Michael Roth
2011-06-23 12:00 ` Avi Kivity
2011-06-23 14:54 ` Michael Roth
2011-06-23 15:09 ` Avi Kivity
2011-06-23 15:50 ` Michael Roth
2011-06-23 15:25 ` Anthony Liguori
2011-06-23 15:52 ` Avi Kivity
2011-06-27 0:24 ` Natalia Portillo
2011-06-23 11:31 ` Jan Kiszka
2011-06-23 14:41 ` Michael Roth
2011-06-23 11:14 ` Ronen Hod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110623113835.GC14307@redhat.com \
--to=berrange@redhat.com \
--cc=agl@linux.vnet.ibm.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=bsarathy@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pmyers@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).