Hi, On Mon, Oct 07, 2019 at 02:40:17PM +0200, Mirko wrote: > The problem seems related to systemd starting. > > I have tried to find a solutions by myself but without success.
In my case, this helped: 1. set unix_sock_dir = "/run/libvirt" in /etc/libvirt/libvirtd.conf 2. systemctl stop libvirtd-admin.socket libvirtd-ro.socket libvirtd-tcp.socket libvirtd-tls.socket libvirtd.socket virtlockd-admin.socket virtlockd.socket virtlogd-admin.socket virtlogd.socket libvirtd.service 3. systemctl start libvirtd.service "service libvirtd start" still doesn't work. (Additionally, one must be extra careful to manually stop all libvirt networks and restart firewalld before attempting to restart libvirtd, otherwise it will refuse to start the network afterwards, but that's a separate regression.) Seems to me that the "[4dcbe93] Revert "Disable libvirtd socket activation" (Closes: #935883)" entry in changelog is what broke this. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935883#8 claims that socket activation actually works fine, but it does not, and the Revert should probably be Reverted again. -- Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/
