From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: dlaor@redhat.com
Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted
Date: Sat, 10 Jan 2009 12:22:06 -0600 [thread overview]
Message-ID: <4968E74E.5040905@codemonkey.ws> (raw)
In-Reply-To: <20090110021811.GJ1972@shareable.org>
Jamie Lokier wrote:
> Daniel P. Berrange wrote:
>
>> 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.
>
When dealing with older OSes, there really no limit in terms of what we
can do. For instance, there's no reason that the backported version of
the virtio-net driver cannot expose a chardev interface if the distro
doesn't have the appropriate configuration.
But we also have to think about how to support newer platforms and newer
kernels and this will often mean that we have to make intrusive changes
so that the integration makes everyone happy. This does not mean that
we cannot support older platforms though, we just have to do it a little
differently on the older platforms.
You cannot get around having a kernel module to support something like
vmchannel so that's always going to be a requirement. A completely
userspace approach ala the VMware backdoor hackery is just too hideous.
Regards,
Anthony Liguori
> 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 18:22 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
2009-01-10 18:22 ` Anthony Liguori [this message]
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=4968E74E.5040905@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).