From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=39825 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OLzkq-0004Sz-Ow for qemu-devel@nongnu.org; Tue, 08 Jun 2010 10:26:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OLzki-0000Kf-91 for qemu-devel@nongnu.org; Tue, 08 Jun 2010 10:26:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37241) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OLzki-0000KV-2L for qemu-devel@nongnu.org; Tue, 08 Jun 2010 10:26:04 -0400 Message-ID: <4C0E52ED.60305@redhat.com> Date: Tue, 08 Jun 2010 16:25:49 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] configure: add an option to disable vlans References: <20100607150309.GA13369@redhat.com> <201006071716.31103.paul@codesourcery.com> <20100607161730.GB11177@redhat.com> <201006071742.56312.paul@codesourcery.com> <4C0D23B5.3050605@codemonkey.ws> <20100607192059.GA14490@redhat.com> <4C0D5959.5010303@codemonkey.ws> <20100608110953.GA21119@redhat.com> <4C0E3F63.6090103@codemonkey.ws> In-Reply-To: <4C0E3F63.6090103@codemonkey.ws> 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: qemu-devel@nongnu.org, Paul Brook , "Michael S. Tsirkin" On 06/08/10 15:02, Anthony Liguori wrote: > On 06/08/2010 06:09 AM, Michael S. Tsirkin wrote: >> On Mon, Jun 07, 2010 at 03:40:57PM -0500, Anthony Liguori wrote: >>> On 06/07/2010 02:21 PM, Michael S. Tsirkin wrote: >>>> So I see two ways to go forward: switch default value in my patch, >>>> or disable vlans unconditionally. >>>> >>> The problem with disabling vlans unconditionally is that you break -net >>> socket and -net dump. >> -netdev socket seems to be supported. No? > > Sure, but it's of limited utility in the absence of vlans. A typical > thing to do with -net socket would be to launch one instance of qemu > with -net user, -net socket, and -net nic. Another qemu would be > launched with -net socket and -net nic connected to the previous > instance. Now you've got a working virtual network with external access. > > -netdev socket alone won't get you this. I see three possible options to handle this. (1) Write a hub (or morph the current vlan code into this). Then you can do something like: qemu -netdev socket,id=p1 \ -netdev user,id=p2 \ -netdev dump,id=p3 \ -switch peer=p1,peer=p2,monitor=p3,port=p4 \ -device $nic,netdev=p4 (2) Implement the same as external daemon which can be combined with -netdev socket. (3) Just point people who need this to the various virtual switch projects (vde, ...) they can use and drop vlan. cheers, Gerd