From: Eric Blake <eblake@redhat.com>
To: Greg Kurz <groug@kaod.org>, Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Jason Wang <jasowang@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu v2] tap: Allow specifying a bridge
Date: Wed, 14 Sep 2016 10:12:58 -0500 [thread overview]
Message-ID: <db0c070f-824f-fd86-8890-4ccbda4c0c5f@redhat.com> (raw)
In-Reply-To: <20160914161724.7d3ad28b@bahia>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On 09/14/2016 09:17 AM, Greg Kurz wrote:
> 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:
Yes, but there was still my other comment that:
>> +++ b/qapi-schema.json
>> @@ -2575,6 +2575,8 @@
>> #
>> # @downscript: #optional script to shut down the interface
>> #
>> +# @br: #optional bridge name
this is missing a '(since 2.8)' designator. Perhaps the maintainer can
supply it without needing a v3.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-09-14 15:13 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
2016-09-14 15:12 ` Eric Blake [this message]
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=db0c070f-824f-fd86-8890-4ccbda4c0c5f@redhat.com \
--to=eblake@redhat.com \
--cc=aik@ozlabs.ru \
--cc=groug@kaod.org \
--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.