From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LLiTY-0002aD-Kx for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:22:24 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LLiTW-0002a1-82 for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:22:23 -0500 Received: from [199.232.76.173] (port=44310 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LLiTW-0002Zy-2j for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:22:22 -0500 Received: from an-out-0708.google.com ([209.85.132.249]:49478) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LLiTV-0004Eg-OH for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:22:21 -0500 Received: by an-out-0708.google.com with SMTP id c38so4254520ana.37 for ; Sat, 10 Jan 2009 10:22:20 -0800 (PST) Message-ID: <4968E74E.5040905@codemonkey.ws> Date: Sat, 10 Jan 2009 12:22:06 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted References: <4964EC55.4000507@codemonkey.ws> <20090107184103.GA19406@redhat.com> <496501CD.8060202@codemonkey.ws> <20090107194633.GB19406@redhat.com> <49665AE7.3000708@codemonkey.ws> <20090108212652.GB22504@redhat.com> <49667330.5070001@codemonkey.ws> <20090108224942.GA12848@shareable.org> <496688D9.1040708@redhat.com> <20090109104154.GA5164@redhat.com> <20090110021811.GJ1972@shareable.org> In-Reply-To: <20090110021811.GJ1972@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: dlaor@redhat.com 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 > > >