From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1My77y-0008UD-OM for qemu-devel@nongnu.org; Wed, 14 Oct 2009 12:55:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1My77t-0008P5-PM for qemu-devel@nongnu.org; Wed, 14 Oct 2009 12:55:06 -0400 Received: from [199.232.76.173] (port=55552 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1My77t-0008On-B1 for qemu-devel@nongnu.org; Wed, 14 Oct 2009 12:55:01 -0400 Received: from mail2.shareable.org ([80.68.89.115]:58056) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1My77s-0001xp-Vn for qemu-devel@nongnu.org; Wed, 14 Oct 2009 12:55:01 -0400 Date: Wed, 14 Oct 2009 17:54:47 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: [PATCH-updated] qemu/net: add raw backend Message-ID: <20091014165447.GA19784@shareable.org> References: <20091014143415.GA29937@redhat.com> <4AD5E449.9070301@codemonkey.ws> <20091014151406.GA17062@shareable.org> <4AD5F51E.7040907@codemonkey.ws> <20091014161424.GA30308@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091014161424.GA30308@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Or Gerlitz , Arnd Bergmann , qemu-devel@nongnu.org Michael S. Tsirkin wrote: > > The fact that network manager does work well with bridged interfaces is > > a network manager bug. > > Network manager was just one example. Even if network manager and all other configuration programs are fixed to handle a bridge, it's still quite fiddly to configure them. I find I have to use - bridges to an uplink interface for some VMs (guest has IP on same network as host, fixed host interfaces, typically in servers) - bridges attached to changing uplink for some VMs (laptop, where the main internet uplink changes between eth0/wlan0/ppp0/bnep0 according to available signals) - no bridge at all (just routing tap, used on all sorts of machines) for VMs needing to run on host-local IPs and talk to the host, and maybe NAT to the internet - bridges not attached to any host interface, just multiple tap interfaces, used to connect guests with host-local IPs that must see each other's broadcasts The corresponding iptables is rather tricky too. > > It's getting fixed so in the near future, tap will satisfy all of > > these requirements. That will be really nice if it does. -- Jamie