Fresh install of Tumblweed; selected KVM in installer; virt-manager won't connect to socket

English Virtualization
1

Hey folks. Long time Linux server user. Recently moved from Windows 10 to Debian + KDE as my daily driver. Now moved to OpenSUSE.

I selected KVM from the installer. But when I open virt-manager I see this error. I’m not sure of the OpenSUSE way to fix?

image

I do not see any folder /var/run/libvirt:

desk:~ # ls -la /var/run/lib*
ls: cannot access '/var/run/lib*': No such file or directory
desk:~ #

Google isn’t helping much. I don’t want to muck stuff up as I don’t know the OpenSUSE way of doing things yet.

2

@imthenachoman Hi and welcome to the Forum :smile:
Is libvirtd installed and running systemctl status libvirtd?

3

Yast to install KVM Hypervisor libvirt-daemon not installed from GUI or pattern kvm_server kvm_tools - English / Virtualization - openSUSE Forums

4

@arvidjaar Thank you very much. That seems to have fixed it.

@malcolmlewis What @arvidjaar posted helped. Thanks!

5

I have the same problem, but the link that was posted with a solution did not work for me. I already had libvirt-daemon installed. I reloaded it and restarted libvirtd.service and I still get the error: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directoryerror.

Edit: Got it fixed. Had to go into su in order to get any of those commands to actually work otherwise it went on an authentication loop.

This could definitely be easier. Yast2 for one could actually install libvirtd, or at least say that it’s not going to.

6

I don’t know if that’s the case but I just saw that libvirtd is dying - not by its conf but due to systemd/dnsmasq set to timeout at 120 seconds.

The trick meanwhile is to edit /usr/lib/systemd/system/libvirtd.service and change:
Environment=LIBVIRTD_ARGS=“–dnsmasq timeout=120” to Environment=LIBVIRTD_ARGS=""
Restart the daemon and libvirt won’t hangout anymore.