From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyQRF-0000vU-Mr for qemu-devel@nongnu.org; Thu, 15 Oct 2009 09:32:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyQRB-0000rX-Ej for qemu-devel@nongnu.org; Thu, 15 Oct 2009 09:32:17 -0400 Received: from [199.232.76.173] (port=37186 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyQRB-0000rQ-Ap for qemu-devel@nongnu.org; Thu, 15 Oct 2009 09:32:13 -0400 Received: from fg-out-1718.google.com ([72.14.220.157]:41530) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MyQRA-0002lJ-Us for qemu-devel@nongnu.org; Thu, 15 Oct 2009 09:32:13 -0400 Received: by fg-out-1718.google.com with SMTP id 22so1531321fge.10 for ; Thu, 15 Oct 2009 06:32:09 -0700 (PDT) Message-ID: <4AD72453.1050209@codemonkey.ws> Date: Thu, 15 Oct 2009 08:32:03 -0500 From: Anthony Liguori MIME-Version: 1.0 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> <4AD65684.3010403@codemonkey.ws> <20091015075612.GB32003@redhat.com> In-Reply-To: <20091015075612.GB32003@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Raw vs. tap List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: kvm-devel , qemu-devel@nongnu.org, Paul Brook , Jens Osterkamp , Sridhar Samudrala Michael S. Tsirkin wrote: > On Wed, Oct 14, 2009 at 05:53:56PM -0500, Anthony Liguori wrote: > >> I would be much more inclined to consider >> taking raw and improving the performance long term if guest<->host >> networking worked. This appears to be a fundamental limitation though >> and I think it's something that will forever plague users if we include >> this feature. >> > > In fact, I think it's fixable with a raw socket bound to a macvlan. > Would that be enough? > What setup does that entail on the part of a user? Wouldn't we be back to square one wrt users having to run archaic networking commands in order to set things up? Regards, Anthony Liguori