Virt Manager: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock'
Since ~August 26th, I've been having issues running virt manager on the latest builds of Wayblue and other Bluebuild based systems. I get the warning
Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock' despite all of the appropriate packages being layered correctly and most of the advice I find online for other linux systems (changing the permissions of said file) seem to fail. Notably, my system is missing that file in both 08262024 (the non working image) and 08212024 (where virt manager is still working, as expected.)
Anybody have any advice for fixing this? Thanks to ostree I'm not pressed for time or anything, but it would be nice to have it working on newer operating system images. 🙂Solution:Jump to solution
Have you tried enabling virt-manager services?
```
systemctl enable virtnetworkd.socket virtstoraged.socket virtnodedevd.socket
...
4 Replies
Solution
Have you tried enabling virt-manager services?
I haven't done all of those, just virtnetworkd. I can try that later.
I use virt-manager in my image too, but it is started with administrator priviliges
you could try with sudo
i think it's just a config problem on my end, but trying couldn't hurt
So I found some time to boot into the latest and restarting the systemd services worked, though I'd be curious to know what that would change between build configurations. Either way, thanks for the support!