From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LM0zL-0005Z5-LL for qemu-devel@nongnu.org; Sun, 11 Jan 2009 09:08:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LM0zK-0005Yn-Nv for qemu-devel@nongnu.org; Sun, 11 Jan 2009 09:08:27 -0500 Received: from [199.232.76.173] (port=42600 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LM0zK-0005Yk-KD for qemu-devel@nongnu.org; Sun, 11 Jan 2009 09:08:26 -0500 Received: from mail.gmx.net ([213.165.64.20]:35236) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LM0zJ-0001BM-UL for qemu-devel@nongnu.org; Sun, 11 Jan 2009 09:08:26 -0500 Message-ID: <4969FD59.10509@gmx.net> Date: Sun, 11 Jan 2009 15:08:25 +0100 From: Carl-Daniel Hailfinger MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted References: <496501CD.8060202@codemonkey.ws> <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> <4968E74E.5040905@codemonkey.ws> <20090111045524.GB15975@shareable.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 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 On 11.01.2009 08:10, Blue Swirl wrote: > On 1/11/09, Jamie Lokier wrote: > >> > 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. >> >> Sure, but don't make it _deliberately_ hard to support >> older/obscure/can't-compile-a-kernel-module guests by designing >> something that's obviously going to require a totally different >> mechanism on those other guests. It would make it unnecessarily hard >> to integrate diverse guests with management apps from different >> authors if they do adopt the vmchannel mechanism. >> > > I think a serial port device should be universally supported by any OS > and it's portable to many systems. Older OS may accidentally enable > forwarding between the trusted nic and other nics, this doesn't happen > with serial lines. > I remember the old days of DOS networking where the Kirschbaum-Netz software provided some sort of routed/forwarded networking between PCs over serial ports. It was a default on choice in many corporate and private "LANs" in Germany at the beginning of the last decade. Except for machines with that software (which is really hard to get nowadays), my concern should be a non-issue, especially for virtual machines which are unlikely to have such software installed. Regards, Carl-Daniel -- http://www.hailfinger.org/