From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyLA7-0005Tx-Em for qemu-devel@nongnu.org; Thu, 15 Oct 2009 03:54:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyLA2-0005Se-Hq for qemu-devel@nongnu.org; Thu, 15 Oct 2009 03:54:14 -0400 Received: from [199.232.76.173] (port=42696 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyLA2-0005Sb-Ew for qemu-devel@nongnu.org; Thu, 15 Oct 2009 03:54:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48248) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MyLA1-00056E-T7 for qemu-devel@nongnu.org; Thu, 15 Oct 2009 03:54:10 -0400 Date: Thu, 15 Oct 2009 09:51:48 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: Release plan for 0.12.0 Message-ID: <20091015075148.GA32003@redhat.com> References: <4AC29E4D.80707@us.ibm.com> <200910081555.40897.jens@linux.vnet.ibm.com> <4ACDF550.1020502@codemonkey.ws> <20091014132154.GA29037@redhat.com> <4AD5DD6B.2030703@codemonkey.ws> <20091014142453.GA29798@redhat.com> <20091014151917.GB17062@shareable.org> <20091014155018.GB30179@redhat.com> <1255554600.20366.9.camel@w-sridhar.beaverton.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1255554600.20366.9.camel@w-sridhar.beaverton.ibm.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sridhar Samudrala Cc: Anthony Liguori , kvm-devel , qemu-devel@nongnu.org, Paul Brook , Jens Osterkamp On Wed, Oct 14, 2009 at 02:10:00PM -0700, Sridhar Samudrala wrote: > On Wed, 2009-10-14 at 17:50 +0200, Michael S. Tsirkin wrote: > > On Wed, Oct 14, 2009 at 04:19:17PM +0100, Jamie Lokier wrote: > > > Michael S. Tsirkin wrote: > > > > On Wed, Oct 14, 2009 at 09:17:15AM -0500, Anthony Liguori wrote: > > > > > Michael S. Tsirkin wrote: > > > > >> Looks like Or has abandoned it. I have an updated version which works > > > > >> with new APIs, etc. Let me post it and we'll go from there. > > > > >> > > > > >> > > > > >>> I'm generally inclined to oppose the functionality as I don't think > > > > >>> it offers any advantages over the existing backends. > > > > >>> > > > > >> > > > > >> I patch it in and use it all the time. It's much easier to setup > > > > >> on a random machine than a bridged config. > > > > >> > > > > > > > > > > Having two things that do the same thing is just going to lead to user > > > > > confusion. > > > > > > > > They do not do the same thing. With raw socket you can use windows > > > > update without a bridge in the host, with tap you can't. > > > > > > On the other hand, with raw socket, guest Windows can't access files > > > on the host's Samba share can it? So it's not that useful even for > > > Windows guests. > > > > I guess this depends on whether you use the same host for samba :) > > > > > > > If the problem is tap is too hard to setup, we should try to > > > > > simplify tap configuration. > > > > > > > > The problem is bridge is too hard to setup. > > > > Simplifying that is a good idea, but outside the scope > > > > of the qemu project. > > > > > > I venture it's important enough for qemu that it's worth working on > > > that. Something that looks like the raw socket but behaves like an > > > automatically instantiated bridge attached to the bound interface > > > would be a useful interface. > > > > I agree, that would be good to have. > > Can't we bind the raw socket to the tap interface instead of the > physical interface and allow the bridge config to work. We can, kind of (e.g. with veth) but what's the point then? > Thanks > Sridhar > > > > > > > I don't have much time, but I'll help anybody who wants to do that. > > > > > > -- Jamie > > -- > > To unsubscribe from this list: send the line "unsubscribe kvm" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html