I have a VM set to start on boot, and libvirtd itself does indeed start. However, qemu:///system fails to come up at boot, along with all of its VMs. If I try to access it in virt-manager, I get a connection refused error on /var/run/libvirt/libvirt-sock . Web searches have come up with results with remedies for /var/run/libvirt/sock not existing (but it exists in my case), and for other errors in connecting to the socket than "connection refused", but I haven't found any remedy for exactly this issue.
Simply restarting libvirtd does bring up qemu:///system and its VMs, but this is a manual step after boot. It almost seems like libvirtd is being brought up before one of its prerequisites, or something like that.
Can anyone provide insight?
Simply restarting libvirtd does bring up qemu:///system and its VMs, but this is a manual step after boot. It almost seems like libvirtd is being brought up before one of its prerequisites, or something like that.
Can anyone provide insight?