From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N65aT-0007TH-3J for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:53:29 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N65aN-0007La-Vz for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:53:28 -0500 Received: from [199.232.76.173] (port=58898 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N65aN-0007LP-QE for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:53:23 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40831) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N65aN-0003lM-9i for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:53:23 -0500 Date: Thu, 5 Nov 2009 16:53:18 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu Message-ID: <20091105165318.GL689@redhat.com> References: <1257294485-27015-1-git-send-email-aliguori@us.ibm.com> <4AF2E247.3090409@redhat.com> <4AF2E7CE.8010506@us.ibm.com> <20091105151154.GF689@redhat.com> <4AF2EBBB.7070605@redhat.com> <4AF2F674.6080205@us.ibm.com> <4AF2FB52.2090305@redhat.com> <4AF2FD10.7050607@us.ibm.com> <4AF2FEE6.6000501@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AF2FEE6.6000501@redhat.com> Reply-To: "Daniel P. Berrange" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Mark McLoughlin , Anthony Liguori , Arnd Bergmann , Juan Quintela , Dustin Kirkland , qemu-devel@nongnu.org, Michael Tsirkin On Thu, Nov 05, 2009 at 06:35:50PM +0200, Avi Kivity wrote: > On 11/05/2009 06:28 PM, Anthony Liguori wrote: > >>Because anything special the management tools wants done (as simple > >>as remembering the interface name so it can collect statistics and > >>associate them with the guest) will render the helper unusable. The > >>helper is pure glue so it will be very hard to generalize. > > > > > >It can get the interface names via info network. > > > >But let's make this more concrete, what features cannot be implemented? > > > > Well, with info network and running the guest stopped, everything's > doable. But it's a rather roundabout way compared to creating the > interface, configuring the !@#$%^ out of it, and passing it on to the guest. > > btw, for network hotplug, you'll need to create/config/pass the > interface, since you can't stop the guest. Indeed the hotplug scenario is a bit of a problem in this model, since libvirt needs to be able to setup iptables & ebtables rules between creating the device & giving it to the guest. 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 :|