All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: add an option to disable vlans
Date: Tue, 08 Jun 2010 16:25:49 +0200	[thread overview]
Message-ID: <4C0E52ED.60305@redhat.com> (raw)
In-Reply-To: <4C0E3F63.6090103@codemonkey.ws>

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

  parent reply	other threads:[~2010-06-08 14:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 15:03 [Qemu-devel] [PATCH] configure: add an option to disable vlans Michael S. Tsirkin
2010-06-07 16:16 ` Paul Brook
2010-06-07 16:17   ` Michael S. Tsirkin
2010-06-07 16:42     ` Paul Brook
2010-06-07 16:52       ` Anthony Liguori
2010-06-07 19:21         ` Michael S. Tsirkin
2010-06-07 20:40           ` Anthony Liguori
2010-06-07 20:58             ` Michael S. Tsirkin
2010-06-07 21:37               ` Anthony Liguori
2010-06-07 21:57                 ` Anthony Liguori
2010-06-08 12:13                   ` Michael S. Tsirkin
2010-06-08 13:03                     ` Anthony Liguori
2010-06-08 13:07                       ` Michael S. Tsirkin
2010-06-08 11:09             ` Michael S. Tsirkin
2010-06-08 13:02               ` Anthony Liguori
2010-06-08 13:14                 ` Michael S. Tsirkin
2010-06-08 14:25                 ` Gerd Hoffmann [this message]
2010-06-08 14:37                   ` Paul Brook
2010-06-08 18:01                     ` Anthony Liguori
2010-06-07 17:41       ` Michael S. Tsirkin
2010-06-09  7:44         ` Markus Armbruster
2010-06-10  7:20           ` Chris Webb
2010-06-10  8:43             ` Michael S. Tsirkin
2010-06-08 12:17   ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C0E52ED.60305@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.