Re: [ovirt-users] ovirt 4.2.2-rc3 switching from legacy to OVS..

> I know OVS is Experimental, but it worked in 4.1.x, and now we have to do a > step back to legacy bridge just to use 4.2.x, which in a vlan environment > just wreaks havoc (every VLAN need's a unique mac assigned to the bridge, > which vdsm does not do, so suddenly you get the kernel complaining about > seeing it's mac address several times.) Could you elaborate on this issue? What is wrong with a bridge that learns its mac from its underlying device? What wold like Vdsm to do, in your opinion? You can file a bug (or even send a patch) if there is a functionality that you'd like to fix.