[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] Setting a interface name with qemu-bridge-helper?

From: Narcis Garcia
Subject: Re: [Qemu-discuss] Setting a interface name with qemu-bridge-helper?
Date: Sun, 14 Jan 2018 11:25:31 +0100

I think vlan number links different VM instances in a same virtual net
(as physical cables) VM1 & VM2 in vlan=0 ; VM3 in vlan=1

With bridge I do before launching Qemu:
$ tunctl -u user -g kvm -t vm1net0
$ brctl addif lanbr0 vm1net0

PD: Please, reply ever to mailing list address.

El 13/01/18 a les 17:51, Shaun Reitan ha escrit:
> Do you increment the VLAN for each vm? Also, if you do it that way you
> have to have your own ifup and ifdown scripts to add the vm to the
> bridge don't you?
> ------ Original Message ------
> From: "Narcis Garcia" <address@hidden>
> To: address@hidden
> Sent: 1/13/2018 4:26:42 AM
> Subject: Re: [Qemu-discuss] Setting a interface name with
> qemu-bridge-helper?
>> I use the syntax:
>> -net tap,vlan=0,ifname=vm1net0
>> El 13/01/18 a les 01:34, Shaun Reitan ha escrit:
>>> When starting vm's with '-netdev bridge,id=net0,br=br0' each vm is given
>>> a tapX interface name and from what I can tell, there is no simple way
>>> to figure out which interface belongs to which VM.
>>> I'd like to see a name option added to it which would be passed along to
>>> the qemu-bridge-helper.  Something like '-netdev
>>> bridge,id=net0,br=br0,name=vm1net0' or '-netdev
>>> bridge,id=net0,br=br0,ifname=vm1net0'
>>> Any reason why setting the tap's interface name was left out before I go
>>> attempting to patch this functionality in? Or maybe is there a fast and
>>> simple way to get the tap interface of the VM
>>> -- 
>>> Shaun Reitan
>>> NDCHost.com

reply via email to

[Prev in Thread] Current Thread [Next in Thread]