From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LzaPc-0001Yi-CJ for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:51:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LzaPX-0001YJ-L4 for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:51:07 -0400 Received: from [199.232.76.173] (port=57408 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LzaPX-0001YG-GB for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:51:03 -0400 Received: from mx2.redhat.com ([66.187.237.31]:45886) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LzaPX-0003pC-1U for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:51:03 -0400 Message-ID: <49F9E48B.2070906@redhat.com> Date: Thu, 30 Apr 2009 20:48:59 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1239812969-8320-2-git-send-email-markmc@redhat.com> <200904291137.57852.paul@codesourcery.com> <49F9AB7C.7020803@redhat.com> <200904301702.32282.paul@codesourcery.com> <49F9D2B3.60707@us.ibm.com> <49F9DBCC.3030906@us.ibm.com> <49F9E3CB.4000604@web.de> In-Reply-To: <49F9E3CB.4000604@web.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 9/9] Introduce VLANClientState::cleanup() List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Mark McLoughlin , Anthony Liguori , Marcelo Tosatti , Markus Armbruster , qemu-devel@nongnu.org, Blue Swirl , Paul Brook Jan Kiszka wrote: > Anthony Liguori wrote: > >> Blue Swirl wrote: >> >>> On 4/30/09, Anthony Liguori wrote: >>> -net pointopoint,tap,nic,model=virtio ? >>> >>> >> Or perhaps: >> >> -net tap,vlan=off,id=1234 -net nic,model=virtio,vlan=off,id=1234 >> >> > > That would only allow one such pair per VM. > I'm guessing that's what id= is for. > Why not keeping all the existing infrastructure, just locking a vlan > against becoming more than a point-to-point link once some conflicting > optimization was applied? That should be easy to implement and to > explain to the user. > I still haven't seen a real life usecase for >2 terminals on a vlan. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.