[[6.12.4] (VM) Libvirt service failure (after update)]

Hello

 

 

Some have fixed that error by removing the virt-manager docker.

Others seemed to have success by shutting down the docker service first.

 

That did not fix it for me, but this did (on 6.11.5):

 

virtlog did not show anything extra each time I tried to disable/enable the service, which seems to be an issue on it's own

Only my syslog showed this:

 

Quote

Nov  3 11:36:09 xxxxxxxxxx  emhttpd: shcmd (2138): /etc/rc.d/rc.libvirt start
Nov  3 11:36:09 xxxxxxxxxx  root: virtlockd is already running...

What worked for me was:

 

- Put the service in disable in the GUI and apply

- Manually kill these processes:

root@xxxxxxxx:/var/run/libvirt# ps aux | grep libvirt
root      9216  0.0  0.0  31920  9448 ?        S    11:38   0:00 /usr/sbin/virtlockd -d -f /etc/libvirt/virtlockd.conf -p /var/run/libvirt/virtlockd.pid
root      9221  0.0  0.0  31920  9564 ?        S    11:38   0:00 /usr/sbin/virtlogd -d -f /etc/libvirt/virtlogd.conf -p /var/run/libvirt/virtlogd.pid

- In console go to /var/run/libvirt/ (or /run/libvirt)

- Delete/rename the directory /var/run/libvirt/libvirtsock (not even sure why it's there, was created on boot)

- Delete/rename the .pid files virtlockd.pid & virtlogd.pid

- Then put the service in the GUI back to enable and Apply

 

This somehow enabled the socket to be used for libvirt, and made it so the system recognized that the other two processes were not running.

I'm not sure if there a better way to do this, or if all steps were needed, as I am not an experienced user, but I was very glad to do this without removing my libvirt.img file and starting over.