You are not logged in.
I updated from libvirt 1.2.21-1 to the new libvirt 1.3.0 today.
After the upgrade libvirt won't start my domain. It errors out with the following error:
Error starting domain: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': No such file or Directory
I have temporarily solved the issue by downgrading the libvirtd package back to 1.2.21-1.
Can i fix this issue (through some config, post upgrade tinkering), or is it simply a bug?
Last edited by mbirkis (2015-12-14 18:44:20)
Offline
The problem lies with virtlogd.socket not getting started along with
libvirtd.service.
Start virtlogd.socket manually:
# systemctl start virtlogd.socket
Offline
Thank's didn't think of it
By the way, should we consider enabling it at startup ?
An Arch Linux enthousiast and a Linux fan in general, mostly interrested in command line use, security issues, code learning and networks.
Offline
The problem lies with virtlogd.socket not getting started along with
libvirtd.service.Start virtlogd.socket manually:
# systemctl start virtlogd.socket
This solves the issue, thanks a lot
Marking as solved.
Offline
I've been starting this by hand for a few years now. Luckily I very rarely have to reboot my VM host. Just realized that the libvirtd unit now installs virtlogd.socket (probably has for years). I just needed to re-enable libvirtd.service:
systemctl enable libvirtd.service
Offline