how to deal with bridge device kernel module removal
Hi everyone,
I've come to a topic that we discussed some time ago but we did not
choose any path to follow since then.
Here's the case. I'm testing in a network with one virtual host that's running
on dom0 that acts both as the controller and a slave machine, too.
There's a bridge device on this multi-role machine involved in testing. The
bridge device gets configured but at the end of the test this device gets
cleaned up and bridge kernel module gets removed, too. This results in breaking
the libvirt's networking infrastructure for the guest and the libvirt's network
has to be reinitialized.
I know, not a typical use case but here's another more realistic.
A network with a bare-metal host hosting two guests (deployed in the <task>
part of the recipe) that are sending some data through dom0 to another
bare-metal host.
The solution to this is removing the _modulename from the bridge device code.
What's your opinion on this?
-Jan