Here a few things I'd want you (@robin) to try and report how that works for you.
First of all is this reproducible, e.g. if your reboot the computer do you get back into the same problem state? Second when in the state that virt-manager can't connect could you try on the command line to issue. $ virsh list --all Does that hang or work showing your guests? Does the virsh call maybe even unblock your waiting virt-manager? Third - does adding a new connection in virt-manager get it done as well? Via "File" -> "Add connection" Note: the warnings on restart are fine, libvirt keeps e.g. dnsmasq processes around and that is systemd notifying you that it found old processes and is regrouping it from before. Note II: the warning of no /dev/kvm is odd. Could you report the following two here if we might miss something (you could miss the module, or the qemu-system or such, not likely since it works later - but just to be sure): $ lsmod $ dpkg -l It almost seems like when libvirt initializes the first time KVM isn't really ready yet as it is missing /dev/kvm. Maybe that puts it into a bad state. Then later it is properly loaded and the libvirt restart makes it pick that up. Maybe providing these can help to time-corelate libvirt start and kvm module: $ dmesg $ journalctl -b 0 -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
