http://bugzilla.opensuse.org/show_bug.cgi?id=1123699 Bug ID: 1123699 Summary: libvirt does not start default network automatically Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs@suse.de Reporter: agraul@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 795623 --> http://bugzilla.opensuse.org/attachment.cgi?id=795623&action=edit libvirt network default not enabled On a recent TW installation (Snapshot 20190125) that uses wicked (server role), the default network was not started automatically. Reproduction: 1. Install yast2-vm 2. Using yast2 virtualization: Install virtualization stack (xen server + tools, kvm server + tools, libvirt-lxc) and enable the virtualization bridge as the yast popup proposes 3. Start the libvirtd systemd service via `systemctl start libvirtd.service` 4. `virsh net-info default` shows that the 'default' network is not active. Expected result: The default network is started when libvirtd is started via systemctl, which allows commands like `virt-install` to succeed. See additional discussion: https://progress.opensuse.org/issues/41093 -- You are receiving this mail because: You are on the CC list for the bug.