All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH qemu v2] tap: Allow specifying a bridge
Date: Wed, 14 Sep 2016 16:17:24 +0200	[thread overview]
Message-ID: <20160914161724.7d3ad28b@bahia> (raw)
In-Reply-To: <1473750714-48290-1-git-send-email-aik@ozlabs.ru>

On Tue, 13 Sep 2016 17:11:54 +1000
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:

> The tap backend is already using qemu-bridge-helper to attach tap
> interface to a bridge but (unlike the bridge backend) it always uses
> the default bridge name - br0.
> 
> This adds a "br" property support to the tap backend.
> 
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> --

Cool ! This allows to easily attach to virbr0 :)

Now that a consensus seems to have been reached for @br:

Reviewed-by: Greg Kurz <groug@kaod.org>
Tested-by: Greg Kurz <groug@kaod.org>

Also Cc'ing the tap device maintainer.

Cheers.

--
Greg

> Changes:
> v2:
> * documented a new member in json and hx
> ---
>  net/tap.c        |  4 +++-
>  qapi-schema.json |  3 +++
>  qemu-options.hx  | 12 +++++++-----
>  3 files changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/net/tap.c b/net/tap.c
> index 6abb962..b6896a7 100644
> --- a/net/tap.c
> +++ b/net/tap.c
> @@ -857,7 +857,9 @@ free_fail:
>              return -1;
>          }
>  
> -        fd = net_bridge_run_helper(tap->helper, DEFAULT_BRIDGE_INTERFACE,
> +        fd = net_bridge_run_helper(tap->helper,
> +                                   tap->has_br ?
> +                                   tap->br : DEFAULT_BRIDGE_INTERFACE,
>                                     errp);
>          if (fd == -1) {
>              return -1;
> diff --git a/qapi-schema.json b/qapi-schema.json
> index c4f3674..dbb9f8f 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -2575,6 +2575,8 @@
>  #
>  # @downscript: #optional script to shut down the interface
>  #
> +# @br: #optional bridge name
> +#
>  # @helper: #optional command to execute to configure bridge
>  #
>  # @sndbuf: #optional send buffer limit. Understands [TGMKkb] suffixes.
> @@ -2604,6 +2606,7 @@
>      '*fds':        'str',
>      '*script':     'str',
>      '*downscript': 'str',
> +    '*br':         'str',
>      '*helper':     'str',
>      '*sndbuf':     'size',
>      '*vnet_hdr':   'bool',
> diff --git a/qemu-options.hx b/qemu-options.hx
> index a71aaf8..0b3ea42 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -1594,10 +1594,11 @@ DEF("netdev", HAS_ARG, QEMU_OPTION_netdev,
>      "                configure a host TAP network backend with ID 'str'\n"
>  #else
>      "-netdev tap,id=str[,fd=h][,fds=x:y:...:z][,ifname=name][,script=file][,downscript=dfile]\n"
> -    "         [,helper=helper][,sndbuf=nbytes][,vnet_hdr=on|off][,vhost=on|off]\n"
> +    "         [,br=bridge][,helper=helper][,sndbuf=nbytes][,vnet_hdr=on|off][,vhost=on|off]\n"
>      "         [,vhostfd=h][,vhostfds=x:y:...:z][,vhostforce=on|off][,queues=n]\n"
>      "         [,poll-us=n]\n"
>      "                configure a host TAP network backend with ID 'str'\n"
> +    "                connected to a bridge (default=" DEFAULT_BRIDGE_INTERFACE ")\n"
>      "                use network scripts 'file' (default=" DEFAULT_NETWORK_SCRIPT ")\n"
>      "                to configure it and 'dfile' (default=" DEFAULT_NETWORK_DOWN_SCRIPT ")\n"
>      "                to deconfigure it\n"
> @@ -1884,8 +1885,8 @@ processed and applied to -net user. Mixing them with the new configuration
>  syntax gives undefined results. Their use for new applications is discouraged
>  as they will be removed from future versions.
>  
> -@item -netdev tap,id=@var{id}[,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,helper=@var{helper}]
> -@itemx -net tap[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,helper=@var{helper}]
> +@item -netdev tap,id=@var{id}[,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,br=@var{bridge}][,helper=@var{helper}]
> +@itemx -net tap[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,br=@var{bridge}][,helper=@var{helper}]
>  Connect the host TAP network interface @var{name} to VLAN @var{n}.
>  
>  Use the network script @var{file} to configure it and the network script
> @@ -1896,8 +1897,9 @@ automatically provides one. The default network configure script is
>  to disable script execution.
>  
>  If running QEMU as an unprivileged user, use the network helper
> -@var{helper} to configure the TAP interface. The default network
> -helper executable is @file{/path/to/qemu-bridge-helper}.
> +@var{helper} to configure the TAP interface and attach it to the bridge.
> +The default network helper executable is @file{/path/to/qemu-bridge-helper}
> +and the default bridge device is @file{br0}.
>  
>  @option{fd}=@var{h} can be used to specify the handle of an already
>  opened host TAP interface.

  parent reply	other threads:[~2016-09-14 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  7:11 [Qemu-devel] [PATCH qemu v2] tap: Allow specifying a bridge Alexey Kardashevskiy
2016-09-13 14:49 ` Eric Blake
2016-09-13 15:39   ` Greg Kurz
2016-09-14  4:23     ` Alexey Kardashevskiy
2016-09-14 13:54       ` Eric Blake
2016-09-14 14:17 ` Greg Kurz [this message]
2016-09-14 15:12   ` Eric Blake
2016-09-22  7:03     ` Jason Wang
2016-09-14 21:04 ` Paolo Bonzini
2016-09-19  0:33   ` Alexey Kardashevskiy
2016-09-19 11:59     ` Paolo Bonzini
2016-09-22  7:05       ` Jason Wang

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=20160914161724.7d3ad28b@bahia \
    --to=groug@kaod.org \
    --cc=aik@ozlabs.ru \
    --cc=jasowang@redhat.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.