Indeed it seems to have been a red herring... Your comment about the
systemd socket gave be the idea to ensure it was enabled and sure enough
the libvirtd.service was enabled and the libvirtd.socket was not, so
libvirtd was exiting without activity and without a socket so I was
unable to start gues
On 8/8/20 10:44 AM, Ken Swenson wrote:
Hello,
I'm having a quite odd issue with libvirtd. I have it set to start on
boot via systemd service, however it seems to fail and the service
'succeeds' and does not continue running the daemon. There is nothing in
the journal logs however the libvirtd
