Ok, so your libvirt really isn't responsive It could be that it only has the socket up in systemd and not starting the service on a connection until you restart it. Or it really is started but not responsible.
I'd recommend to: 1. enable logging in libvirt -> https://wiki.libvirt.org/page/DebugLogs That usually comes down to add to /etc/libvirt/libvirtd.conf: log_level = 1 log_outputs="1:file:/var/log/libvirtd.log" 2. Right after reboot then please: 2.1 check if it is hanging $ virsh list --all 2.2 if it is hanging please report the following $ systemctl status libvirtd.service libvirtd-admin.socket libvirtd-ro.socket libvirtd.socket $ cat /var/log/libvirtd.log P.S. Please consider putting that to text files and attach them to the bug instead of google-docs in a gdrive. It just is more accessible for more people. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
