From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FcVh4-0003Wz-3C for qemu-devel@nongnu.org; Sat, 06 May 2006 18:56:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FcVh3-0003Wl-Bg for qemu-devel@nongnu.org; Sat, 06 May 2006 18:56:09 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FcVh3-0003Wi-6I for qemu-devel@nongnu.org; Sat, 06 May 2006 18:56:09 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FcVhW-0003AB-Nt for qemu-devel@nongnu.org; Sat, 06 May 2006 18:56:38 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FcVgu-0004lY-JM for qemu-devel@nongnu.org; Sun, 07 May 2006 00:56:00 +0200 Received: from cpe-70-116-9-243.austin.res.rr.com ([70.116.9.243]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 May 2006 00:56:00 +0200 Received: from anthony by cpe-70-116-9-243.austin.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 May 2006 00:56:00 +0200 From: Anthony Liguori Date: Sat, 06 May 2006 17:55:51 -0500 Message-ID: References: <20060505215128.4171C1DC197@ravel.n2.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: news Subject: [Qemu-devel] Re: bug reports and suggestions 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 Fri, 05 May 2006 14:51:28 -0700, Don Kitchen wrote: > Next, it seems the *one* thing QEMU lacks that you-know-who does correctly > is networking, specifically bridged mode. I know about creating a tap > device and sticking it into a bridge (really hasn't worked for me, but > that's the subject for a different day.) I use bridging with qemu so I can attest that it works quite well once you get it to work. We face a similar problem in Xen. The solution we've come up with is a *very* complicated script that attempts to reconfigure your networking setup. The problem with this general approach is that how networking is configured is *very* distro-specific. In Xen, we attempt to be generic but in reality, it only works on a very specific set of distros that we frequently test on. VMware faces the same problem (of course). Networking doesn't tend to work well at all unless you're on a supported distro. What's really needed is the NetworkManager equivalent for network configuration. That is, something that has backends for all of the popular distros that can provide a consistent interface to reconfiguring networking. Of course, it all falls apart if you do crazy things locally (like using insane iptables rules) but it would help for the majority of users. Regards, Anthony Liguori