https://bugzilla.suse.com/show_bug.cgi?id=1174936 https://bugzilla.suse.com/show_bug.cgi?id=1174936#c11 --- Comment #11 from James Fehlig --- (In reply to James Fehlig from comment #10)

That's one way, but I _think_ the bridges created by nmcli should be usable in the same fashion as those created via yast+wicked. If you have a working setup, check if the "usual" vif config results in a working interface in a VM. E.g.

<interface type='bridge'> <mac address='52:54:00:24:d4:6a'/> <source bridge='br0'/> <model type='virtio'/> </interface>

I moved my laptop to a wired connection and indeed this works the same as with yast+wicked managed bridges. IOW, once a bridge is created and "up'ed" with nmcli as you've documented, it can be used by VM's as already documented for wicked-manged bridges.

Also, the bridge should be available in virt-manager, for use by new VMs and new vifs added to existing VMs.

virt-manager allows selecting "Bridge device" from the "Network source" drop down, which then allows typing in the bridge name. -- You are receiving this mail because: You are on the CC list for the bug.