Arch Linux

Kody

Member

Registered: 2018-03-13

Posts: 8

Libvirt running, but not creating a socket

After an update libvirt is not creating a socket.
Running systemctl status libvirtd shows that libvirt is running:

● libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/local/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2019-12-04 19:36:40 MST; 12s ago
TriggeredBy: ● libvirtd-ro.socket
             ● libvirtd.socket
             ● libvirtd-admin.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
   Main PID: 3964 (libvirtd)
      Tasks: 17 (limit: 32768)
     Memory: 13.5M
     CGroup: /system.slice/libvirtd.service
             └─3964 /usr/local/sbin/libvirtd

Dec 04 19:36:40 QPC systemd[1]: Started Virtualization daemon.
Dec 04 19:36:40 QPC libvirtd[3964]: libvirt version: 6.0.0
Dec 04 19:36:40 QPC libvirtd[3964]: hostname: QPC
Dec 04 19:36:40 QPC libvirtd[3964]: Libvirt doesn't support VirtualBox API version 6000014

But neither virt-manager nor virsh can connect to the socket. (and I've manually checked, there is no socket at that location)

Verify that the 'libvirtd' daemon is running.

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 956, in _do_open
    self._backend.open(connectauth.creds_dialog, self)
  File "/usr/share/virt-manager/virtinst/connection.py", line 172, in open
    conn = libvirt.openAuth(self._open_uri,
  File "/usr/lib/python3.8/site-packages/libvirt.py", line 104, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

I've tried downgrading the entire system to the last time I updated, and a few other dates just to check but I cannot figure out what the issue is. Can anyone suggest what to look for to resolve this? Most search results are just people forgetting to start libvirtd but I know it is running.

Edit: by running 'sudo libvirtd --help' I was able to get:

libvirt management daemon:

  Default paths:

    Configuration file (unless overridden by -f):
      /usr/local/etc/libvirt/libvirtd.conf

    Sockets:
      /usr/local/var/run/libvirt/libvirt-sock
      /usr/local/var/run/libvirt/libvirt-sock-ro

    TLS:
      CA certificate: /usr/local/etc/pki/CA/cacert.pem
      Server certificate: /usr/local/etc/pki/libvirt/servercert.pem
      Server private key: /usr/local/etc/pki/libvirt/private/serverkey.pem

    PID file (unless overridden by -p):
      /usr/local/var/run/libvirtd.pid

so it looks like everything that used to be in /var/run is now instead in /usr/local/var/run
I was able to get virt-manager to work by creating a symlink and I think I can just move all of my old files over to get everything up and running again but now I'm curious as to why this directory suddenly changed (and also what is the purpose of /usr/local). I was using libvirt-git from the aur before, but since I was getting build errors I switched back to the regular libvirt, could that explain the difference in directory?

Last edited by Kody (2019-12-05 04:47:25)

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,452

Re: Libvirt running, but not creating a socket

Dec 04 19:36:40 QPC libvirtd[3964]: libvirt version: 6.0.0

How is this possible? As at Dec 4 [community] has libvirt 5.9.0-1 and [community-testing] has libvirt 5.10.0-1?

Please post the output of

pacman -Qi libvirt

Kody

Member

Registered: 2018-03-13

Posts: 8

Re: Libvirt running, but not creating a socket

I saw that too and I assumed maybe that referred to an API version or something? I don't think that is the package version but here is the output of 'pacman -Qi libvirt':

Name            : libvirt
Version         : 5.9.0-1
Description     : API for controlling virtualization engines (openvz,kvm,qemu,virtualbox,xen,etc)
Architecture    : x86_64
URL             : https://libvirt.org/
Licenses        : LGPL
Groups          : None
Provides        : None
Depends On      : e2fsprogs  gnutls  iptables  libxml2  parted  polkit  yajl  libpciaccess  udev  dbus  libxau  libxdmcp  libpcap  libcap-ng  curl  libsasl  libgcrypt  libgpg-error  openssl  libxcb
                  gcc-libs  iproute2  libnl  libx11  numactl  gettext  libssh2  netcf  fuse2  glusterfs  ceph-libs  libiscsi
Optional Deps   : ebtables: required for default NAT networking [installed]
                  dnsmasq: required for default NAT/DHCP for guests [installed]
                  bridge-utils: for bridged networking [installed]
                  netcat: for remote management over ssh [installed]
                  qemu [installed]
                  radvd
                  dmidecode [installed]
                  parted [installed]
                  ceph: for ceph support [installed]
                  qemu-block-gluster: for qemu glusterfs support
Required By     : libvirt-glib  libvirt-python  libvirt-python2  virt-viewer
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 41.91 MiB
Packager        : Anatol Pomozov <anatol.pomozov@gmail.com>
Build Date      : Sat 16 Nov 2019 09:32:44 PM MST
Install Date    : Wed 04 Dec 2019 07:09:09 PM MST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

I got all of my virtual machines running again by just moving the config files to the correct folder, now I'm just curious as to what I should have been paying more attention to that caused this directory changing.

Jazztache

Member

Registered: 2022-10-07

Posts: 65

Re: Libvirt running, but not creating a socket

Hello,

If you don't mind me asking, which folder should I move the configs from and to? I am having the same issue, and I would like to see if I can fix it as well.

Thanks