From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LLEoQ-00049E-Qf for qemu-devel@nongnu.org; Fri, 09 Jan 2009 05:41:58 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LLEoP-00048x-6i for qemu-devel@nongnu.org; Fri, 09 Jan 2009 05:41:58 -0500 Received: from [199.232.76.173] (port=40693 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LLEoO-00048u-VR for qemu-devel@nongnu.org; Fri, 09 Jan 2009 05:41:57 -0500 Received: from mx1.redhat.com ([66.187.233.31]:59952) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LLEoO-0003pE-If for qemu-devel@nongnu.org; Fri, 09 Jan 2009 05:41:56 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n09AfuFa018230 for ; Fri, 9 Jan 2009 05:41:56 -0500 Date: Fri, 9 Jan 2009 10:41:54 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted Message-ID: <20090109104154.GA5164@redhat.com> References: <4964EC2B.1080406@codemonkey.ws> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496688D9.1040708@redhat.com> Reply-To: "Daniel P. Berrange" , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dlaor@redhat.com, qemu-devel@nongnu.org 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. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|