From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EMl3m-0000q9-6K for qemu-devel@nongnu.org; Tue, 04 Oct 2005 07:34:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EMl3i-0000mo-71 for qemu-devel@nongnu.org; Tue, 04 Oct 2005 07:34:11 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EMl3g-0000Zp-Qx for qemu-devel@nongnu.org; Tue, 04 Oct 2005 07:34:08 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EMl3f-0005N4-GE for qemu-devel@nongnu.org; Tue, 04 Oct 2005 07:34:07 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.253.219]) by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j94BY6DE029368 for ; Tue, 4 Oct 2005 07:34:06 -0400 (EDT) Date: Tue, 4 Oct 2005 07:34:02 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] tun/tap networking: patch for existing tun Message-ID: <20051004113402.GA7371@jbrown.mylinuxbox.org> References: <20051001131215.GB28444@jbrown.mylinuxbox.org> <433EF5C4.2030801@eclis.ch> <433F92CB.1060600@eclis.ch> <43402ABC.3040805@us.ibm.com> <20051002193912.GB13825@jbrown.mylinuxbox.org> <20051003151425.GC27327@jbrown.mylinuxbox.org> <43417879.5020106@bellard.org> <1128414207.11765.10.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1128414207.11765.10.camel@localhost.localdomain> 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 On Tue, Oct 04, 2005 at 10:23:26AM +0200, Matteo wrote: > That would be a very good idea. I've always thought of installing vde or > any other application to make a network of VMs painfull. Well, i find that a qemu_switch would be more convient as you could set up the network at boot time (like i do with vde now). > Moreover you > then need to configure each host, write scripts... There is only one host. And if u don't use tuntap, then no host configuration is required (remember slirpvde?). Guests have to be configured anyways (tho slirpvde includes a dhcp server). > The integration to > the existing user net would be great for most of the cases. Non trivial > ones will maybe need the fine tuning tun/tap devices allow, but I think > most users want simplicity VDE provides this already. Of course, a user-net based solution for qemu guest networks could do a few things that slirpvde can't (like -redir support). It is definitely worth trying for. For the most part tho, it's just duplicating functionality that we already have. > > Matt?o > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.