Libvirtd Failing to start - Fresh TW install

Hi All,

Looks like I’m having issues with libvirt on a my fresh TW install. :frowning:

I pdated to the latest packages , then I used Yast2 to install KVM & KVM tools on here. After a reboot I was hoping things would just click into place.

The install did give a warning saying NetworkManager prevented bridge from creation, do it manually.
I initially tried doing it with virsh net-dfine. I kept getting errors with that, so I used nmcli and now have my bridge created.

3: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 26:3c:8e:f0:d3:1f brd ff:ff:ff:ff:ff:ff

After I did that I started to look into why virsh didn’t work, checked the libvirtd service health and realized that it was failing.

Jul 28 14:00:51 geckoeggs systemd[1]: Starting Virtualization daemon...
Jul 28 14:00:51 geckoeggs libvirtd[403]: libvirt version: 9.5.0
Jul 28 14:00:51 geckoeggs libvirtd[403]: hostname: geckoeggs
Jul 28 14:00:51 geckoeggs libvirtd[403]: Failed to initialize libnetcontrol.  Management of interface devices is disabled
Jul 28 14:00:51 geckoeggs systemd[1]: Started Virtualization daemon.
Jul 28 14:02:51 geckoeggs systemd[1]: libvirtd.service: Deactivated successfully.

Digging a little deeper I think I see the answer to my own question.

AFAIK, the two don’t coexist. On my Tumbleweed 20160716, libvirtd fails to
initialize libnetcontrol when NetworkManager is enabled

Network Manager is on by default and the underlying goodies of Libvirtd don’t get along with NM.
I’ll try flipping NM off and seeing how things go.
Personally I prefer the old file based ifcfg config from my RedHat Enterprise experience, hopefully it’s similar. :grin:

@PeterChz Hi, how many interfaces do you have? No issues here, but I have two bridges and two physical interfaces for virtual machines.

You can just create as a text file for an nm connection, or use nmtui to create…