http://bugzilla.opensuse.org/show_bug.cgi?id=1123699 http://bugzilla.opensuse.org/show_bug.cgi?id=1123699#c3 --- Comment #3 from Alexander Graul <agraul@suse.com> --- (In reply to James Fehlig from comment #1)
(In reply to Alexander Graul from comment #0)
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
FYI, this bridge has nothing to do with libvirt but is certainly usable via virt-install.
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.
virt-install is not dependent on the default network. It can just as easily use bridges configured with yast, NM, ip command, etc. E.g. 'virt-install ... --network bridge=br0,mac=...'
See additional discussion: https://progress.opensuse.org/issues/41093
That thread has some incorrect information. E.g. libvirt-daemon-config-network has no relationship with and is not affected by NM or wicked.
Thanks for the clarification. -- You are receiving this mail because: You are on the CC list for the bug.