All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: agl@linux.vnet.ibm.com, Stefan Hajnoczi <stefanha@gmail.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 09:54:59 -0500	[thread overview]
Message-ID: <4E0353C3.60600@linux.vnet.ibm.com> (raw)
In-Reply-To: <4E032AC5.2080709@redhat.com>

On 06/23/2011 07:00 AM, Avi Kivity wrote:
> On 06/23/2011 02:08 PM, 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.
>>
>
> Even building the tools would be very hard. In general if you build
> against libc version y, you cannot expect your code to work against libc
> version y-1, unless you take special measures. With other libraries the
> "special measures" may not even be possible.

Nvidia/ATI driver installers might be a good (or bad) precedent, I 
believe they ship a generic blob....need to confirm. We'd want to have a 
controlled environment that's used for building the tools we add to the 
ISO though.

>
> (I'm assuming statically linking the binaries is out of the question)
>

Not totally, but the build environment would need to be carefully 
crafted, and for something like the guest agent which pulls in glib/curl 
I'm not sure how viable that is.

  reply	other threads:[~2011-06-23 14:55 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
2011-06-23 14:46       ` Michael Roth
2011-06-23 12:00     ` Avi Kivity
2011-06-23 14:54       ` Michael Roth [this message]
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=4E0353C3.60600@linux.vnet.ibm.com \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=agl@linux.vnet.ibm.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=avi@redhat.com \
    --cc=bsarathy@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.