From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=47340 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OMc58-0001It-Nt
	for qemu-devel@nongnu.org; Thu, 10 Jun 2010 03:21:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <chris@arachsys.com>) id 1OMc56-0000AP-KP
	for qemu-devel@nongnu.org; Thu, 10 Jun 2010 03:21:42 -0400
Received: from alpha.arachsys.com ([91.203.57.7]:50003)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <chris@arachsys.com>) id 1OMc56-00009t-GW
	for qemu-devel@nongnu.org; Thu, 10 Jun 2010 03:21:40 -0400
Date: Thu, 10 Jun 2010 08:20:56 +0100
From: Chris Webb <chris@arachsys.com>
Subject: Re: [Qemu-devel] [PATCH] configure: add an option to disable vlans
Message-ID: <20100610072056.GP2268@arachsys.com>
References: <20100607150309.GA13369@redhat.com>
	<201006071716.31103.paul@codesourcery.com>
	<20100607161730.GB11177@redhat.com>
	<201006071742.56312.paul@codesourcery.com>
	<20100607174140.GE11177@redhat.com>
	<m3631s645o.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3631s645o.fsf@blackfin.pond.sub.org>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>, "Michael S. Tsirkin" <mst@redhat.com>

Markus Armbruster <armbru@redhat.com> writes:

> "Michael S. Tsirkin" <mst@redhat.com> writes:
> 
> > Everyone ok with disabling vlans with no config option?
> 
> Wrong question.  You got to ask "anyone *not* ok with disabling vlans
> with no config option?"

We do use socket devices in the form

  -net nic,model=e1000,vlan=X,mac=MMM -net socket,vlan=X,mcast=Y:Z

but presumably this can just be rewritten as

  -netdev socket,id=netX,mcast=Y:Z -device e1000,netdev=netX,mac=MMM

It's only the case of a nic connected to multiple backends by a VLAN that's
being deprecated here, not any of the previously supported backends?

Cheers,

Chris.