From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N65JZ-0001em-Ab for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:36:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N65JU-0001YG-J6 for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:36:00 -0500 Received: from [199.232.76.173] (port=54150 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N65JU-0001Xz-Ao for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:35:56 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40495) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N65JT-0001Im-R3 for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:35:56 -0500 Message-ID: <4AF2FEE6.6000501@redhat.com> Date: Thu, 05 Nov 2009 18:35:50 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu 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> In-Reply-To: <4AF2FD10.7050607@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Mark McLoughlin , Arnd Bergmann , Juan Quintela , Dustin Kirkland , qemu-devel@nongnu.org, Michael Tsirkin 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. -- error compiling committee.c: too many arguments to function