From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH qemu-kvm] Add raw(af_packet) network backend to qemu Date: Wed, 27 Jan 2010 10:34:35 +0100 Message-ID: <201001271034.35904.arnd@arndb.de> References: <1264538423.24933.144.camel@w-sridhar.beaverton.ibm.com> <4B5F5594.6080006@codemonkey.ws> <20100127092451.GC3476@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Sridhar Samudrala , avi@redhat.com, markmc@redhat.com, ogerlitz@voltaire.com, kvm@vger.kernel.org, qemu-devel@vger.kernel.org To: "Michael S. Tsirkin" Return-path: Received: from moutng.kundenserver.de ([212.227.126.171]:59584 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751236Ab0A0Jeu (ORCPT ); Wed, 27 Jan 2010 04:34:50 -0500 In-Reply-To: <20100127092451.GC3476@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wednesday 27 January 2010, Michael S. Tsirkin wrote: > I am not sure I agree with this sentiment. The main issue being that > macvtap doesn't exist on all kernels :). macvlan also requires hardware > support, packet socket can work with any network card in promisc mode. To be clear, macvlan does not require hardware support, it will happily put cards into promiscous mode if they don't support multiple mac addresses. > I agree to that. People don't even seem to agree whether it's a raw > socket or a packet socket :) We need a better name for this option: what > it really does is rely on an external device to loopback a packet to us, > so how about -net loopback or -net extbridge? I think -net socket,fd should just be (trivially) extended to work with raw sockets out of the box, with no support for opening it. Then you can have libvirt or some wrapper open a raw socket and a private namespace and just pass it down. If you really want to let qemu open the socket itself, -net socket,raw=eth0 is probably closer to what you want than a new -net xxx option. Arnd