Replies: 2 comments 2 replies
-
I presume this is in relation to the devices creating on the host? I presume the issue is that it's a public network configuration that you are looking to define? otherwise should be able to set I'm afraid I've had trouble getting the public network option to work out the box without a bridged device to use so I'm not really able to test whether exposing the same option in the https://github.com/vagrant-libvirt/vagrant-libvirt/blob/main/lib/vagrant-libvirt/templates/public_interface.xml.erb template would work as expected or cause other issues. |
Beta Was this translation helpful? Give feedback.
-
@mazzy89 I think #1692 might solve this for you if you want to take it for a test to confirm. I do need to add some validation because the libvirt spec says that device names starting with specific prefixes will be ignored, e.g. vnet, but presumably you want to use a different naming scheme anyway. |
Beta Was this translation helpful? Give feedback.
-
I haven't found a way to control virtual interface name created by Libvirt. I have the following use case. A machine which has a physical interface
enp89s0
configured like sothe interface is plugged into a bridge
br0
which hasVLANFiltering
set toon
and the following configuration network configuration
At this point all the VMs created via vagrant-libvirt are placed into the VLAN=166 thanks to the following config
This design allow to have one unique bridge which filter VLANs.
however in this design I find a flaw. before launching the VM we do not know the name of the virtual interface so we need to match them all. In the case of having VMs running in a different VLAN then this would not be possible because even if we have a different bridge for control different VLAN traffic, still the match with the interface would go to select all the interfaces.
At this point then I'm wondering whether there is a way to control the name of the virtual interface created by Libvirt.
Beta Was this translation helpful? Give feedback.
All reactions