Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: virt-manager Failed to connect socket to '/run/libvirt/virtlogd-sock' (Read 599 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

virt-manager Failed to connect socket to '/run/libvirt/virtlogd-sock'

I am trying to use virt-manager to run KVM images.  I have managed to do this on Arch. My formula looks like this

pacman -S qemu-full virt-manager virt-viewer dnsmasq vde2 bridge-utils gnu-netcat libguestfs

After finding artix pkgs  virt-viewer & libguestfs are not available and likely not needed for my use I dropped those.
I have managed to install most of qemu-full from the artix; howver, it seems that it needs qemu-system-aarch64 which depends on a firmware pkg edk2-armvirt, which is not in artix. Can this not be added to the artix repos?

Any way I installed the arch version of edk2-armvirt and that allows qemu-full to install.
However, even after setting up all the required permissions and groups I find that the VMs won't start because of an error

Failed to connect socket to '/run/libvirt/virtlogd-sock

I think that's because libvirtd-runit's run doesn't start up a socket listener. I found a fix here
https://github.com/crc-org/crc/issues/629, so after changing stdio_handler to "file" a VM can start.

Is there a way to use the socket approach? I notice that the systemd setup appears  to provide sockets virtlogd-sock, virtlogd-sock & virtlogd-admin-sock which are missing in artix.
My usage won't be risking file space exhaustion if I use a file for stdio, but is there a way to make these sockets work for someone who wants to run a vm server?

 

Re: virt-manager Failed to connect socket to '/run/libvirt/virtlogd-sock'

Reply #1
Seems like there's a separate runit service to start off the virtlogd daemon which should provide the sockets I need.