Laine Stump c17edaf778 network: properly check for taps that are connected to an OVS bridge ... When libvirtd is restarted, it checks that each guest tap device is still attached to the bridge device that the configuration info says it should be connected to. If not, the tap will be disconnected from [wherever it is] and connected to [wherever it should be]. The previous code that did this did not account for: 1) the IFLA_MASTER attribute in a netdev's ifinfo will be set to "ovs-system" for any tap device connected to an OVS bridge, *not* to the name of the bridge it is attached to. 2) virNetDevRemovePort() only works for devices that are attached to a standard Linux host bridge. If a device is currently attached to an OVS bridge, then virNetDevOpenvswitchRemovePort() must be called instead. This patch remedies those problems, and adds a couple of information log messages to aid in debugging any future problem. Resolves: https://bugzilla.redhat.com/1596176 Signed-off-by: Laine Stump <laine@laine.org> ACKed-by: Michal Privoznik <mprivozn@redhat.com>		2018-07-02 19:57:52 -04:00
..
bridge_driver_linux.c
bridge_driver_nop.c
bridge_driver_platform.c
bridge_driver_platform.h	network: allow opening with network:///system and network:///session URIs	2018-01-31 17:45:01 +00:00
bridge_driver.c	network: properly check for taps that are connected to an OVS bridge	2018-07-02 19:57:52 -04:00
bridge_driver.h	network: remove conditional declarations	2018-02-09 11:05:10 +00:00
default.xml
leaseshelper.c
Makefile.inc.am	make: split network driver build rules into network/Makefile.inc.am	2018-03-05 17:08:36 +00:00