From: Jamie Lokier <jamie@shareable.org>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: dlaor@redhat.com
Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted
Date: Sat, 10 Jan 2009 02:18:11 +0000 [thread overview]
Message-ID: <20090110021811.GJ1972@shareable.org> (raw)
In-Reply-To: <20090109104154.GA5164@redhat.com>
Daniel P. Berrange wrote:
> On Fri, Jan 09, 2009 at 01:14:33AM +0200, Dor Laor wrote:
> > Jamie Lokier wrote:
> > >Anthony Liguori wrote:
> > >
> > >>Are we going to have a standard way of doing this in Linux distros such
> > >>that these nics are treated differently from other nics? Have we gotten
> > >>the appropriate distro folks to agree to this?
> > >>
> > >
> > >That wouldn't work for older distros and Windows anyway. But you
> > >might reasonably want to run apps doing guest-host communication on
> > >older guest distros too, simply as an app, not requiring guest
> > >customisation.
> > >
> > We can make fedora, rhel and libvirt support it. It might be a bit
> > painful but since
> > a network device was chosen for this propose then that's the right way
> > to go.
>
> For new Fedora / RHEL yes, but a large number of people using virt are
> doing so with old OS versions, and the chances of anyone retro-fitting
> all old distros is near zero. You might get it done if they were back
> porting the VirtIO NIC devices to old distros, but almost certainly not
> for arbitrary NIC devices like rtl8139/e1000/etc because its a huge
> QA testing headache to avoid regressions.
In some circles, a major purpose of virtualisation is to run old OS
versions, either copied from machines where the hardware is aging to
keep a working system still working, or for compatibility testing.
Changing a working guest setup isn't cool. Adding a small
monitoring/reporting app (e.g. that shows the machine's load average,
process table, network connections or whatever over a vmchannel) may
be cool, provided it has negligable impact, even if changing its
system configuration is not.
-- Jamie
next prev parent reply other threads:[~2009-01-10 2:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 14:26 [Qemu-devel] [PATCH] mark nic as trusted Gleb Natapov
2009-01-07 15:04 ` Mark McLoughlin
2009-01-07 15:19 ` Gleb Natapov
2009-01-07 15:41 ` Mark McLoughlin
2009-01-07 16:02 ` Gleb Natapov
2009-01-07 16:34 ` Anthony Liguori
2009-01-07 16:50 ` Gleb Natapov
2009-01-07 17:53 ` Anthony Liguori
2009-01-07 17:54 ` Anthony Liguori
2009-01-07 18:41 ` Gleb Natapov
2009-01-07 19:26 ` Anthony Liguori
2009-01-07 19:46 ` Gleb Natapov
2009-01-08 19:58 ` Anthony Liguori
2009-01-08 21:26 ` Gleb Natapov
2009-01-08 21:42 ` Anthony Liguori
2009-01-08 22:49 ` Jamie Lokier
2009-01-08 23:14 ` Dor Laor
2009-01-09 10:41 ` Daniel P. Berrange
2009-01-10 2:18 ` Jamie Lokier [this message]
2009-01-10 18:22 ` Anthony Liguori
2009-01-11 4:55 ` Jamie Lokier
2009-01-11 7:10 ` Blue Swirl
2009-01-11 14:08 ` Carl-Daniel Hailfinger
2009-01-11 15:07 ` Dor Laor
2009-01-11 15:34 ` Blue Swirl
2009-01-11 16:01 ` Dor Laor
2009-01-12 2:20 ` Jamie Lokier
2009-01-12 8:05 ` Gleb Natapov
2009-01-12 12:26 ` Dor Laor
2009-01-10 2:27 ` Jamie Lokier
2009-01-08 23:26 ` Anthony Liguori
2009-01-10 2:31 ` Jamie Lokier
2009-01-10 18:24 ` Anthony Liguori
2009-01-11 4:40 ` Jamie Lokier
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=20090110021811.GJ1972@shareable.org \
--to=jamie@shareable.org \
--cc=berrange@redhat.com \
--cc=dlaor@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).