http://bugzilla.suse.com/show_bug.cgi?id=1123699 http://bugzilla.suse.com/show_bug.cgi?id=1123699#c84 --- Comment #84 from Oliver Kurz <okurz@suse.com> --- Ok, but please keep in mind that this is a regression. As described in https://progress.opensuse.org/issues/41093 the "last good" was openSUSE Tumbleweed 20180910 . As visible in https://openqa.opensuse.org/tests/752406#step/yast_virtualization/19 there was a dialog in "yast2 vm" asking to create and configure a default bridge. https://openqa.opensuse.org/tests/752406#step/yast_virtualization/29 shows that libvirtd is running correctly and shows no error about "Failed to initialize libnetcontrol". So certainly something in the combination of libvirt, wicked, yast2-virtualization is not working as in before and less obvious to the user. I don't see that anything on the side of tests should be changed for this. Starting the network interface manually is a workaround for this bug anyway and also not what for example the documentation on https://doc.opensuse.org/documentation/leap/virtualization/single-html/book.... describes as necessary. -- You are receiving this mail because: You are on the CC list for the bug.