On 2016年09月19日 19:59, Paolo Bonzini wrote:
On 19/09/2016 02:33, Alexey Kardashevskiy wrote:
On 15/09/16 07:04, Paolo Bonzini wrote:
On 13/09/2016 09:11, Alexey Kardashevskiy wrote:
The tap backend is already using qemu-bridge-helper to attach tap
interface to a bridge but (unlike the bridg
On 2016年09月14日 23:12, Eric Blake wrote:
On 09/14/2016 09:17 AM, Greg Kurz wrote:
On Tue, 13 Sep 2016 17:11:54 +1000
Alexey Kardashevskiy 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
On 19/09/2016 02:33, Alexey Kardashevskiy wrote:
> On 15/09/16 07:04, Paolo Bonzini wrote:
>>
>>
>> On 13/09/2016 09:11, Alexey Kardashevskiy 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
>>> t
On 15/09/16 07:04, Paolo Bonzini wrote:
>
>
> On 13/09/2016 09:11, Alexey Kardashevskiy 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" prop
On 13/09/2016 09:11, Alexey Kardashevskiy 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-b
On 09/14/2016 09:17 AM, Greg Kurz wrote:
> On Tue, 13 Sep 2016 17:11:54 +1000
> Alexey Kardashevskiy 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 a
On 09/13/2016 11:23 PM, Alexey Kardashevskiy wrote:
>>>
>>> Also, we don't have to abbreviate; 'bridge-name' may be easier to
>>> understand than 'br', as well as a mention of the default value if the
>>> parameter is not supplied.
>
>
> The existing NetdevBridgeOptions does not do this in json
On Tue, 13 Sep 2016 17:11:54 +1000
Alexey Kardashevskiy 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.
>
On 14/09/16 01:39, Greg Kurz wrote:
> On Tue, 13 Sep 2016 09:49:09 -0500
> Eric Blake wrote:
>
>> On 09/13/2016 02:11 AM, Alexey Kardashevskiy 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
>>>
On Tue, 13 Sep 2016 09:49:09 -0500
Eric Blake wrote:
> On 09/13/2016 02:11 AM, Alexey Kardashevskiy 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.
> >
> > Thi
On 09/13/2016 02:11 AM, Alexey Kardashevskiy 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-
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
--
Changes:
v2:
* documented a new membe
12 matches
Mail list logo