Closed GuiltyDoggy closed 11 hours ago
The libvirtd is not active check checks specifically if the systemd's libvirtd connection works or not as you likely use a user connection it works in virt-manager but nothing is shown cockpit-machines.
I can replicate this locally as well, just stopping all system libvirt services and running a user session VM.
I think we already have an issue on this, and it's related to SELinux on Fedora 41.
A workaround is to setenforce 0
or roll back to Fedora 40 for the time being... unless it was already fixed. (I guess it hasn't if you're still hitting it. I haven't checked recently.)
https://github.com/cockpit-project/cockpit-machines/issues/1818
(Note: This might be a different issue, but it looks very similar: Fedora 41, it says "libvirt is not active" even though it is, etc.)
It is indeed #1818. Sorry for the dupe.
Setenforce 0 fixes it for now.
Thanks for reporting it! It's better to have a duplicate issue than to not have one at all.
Hopefully I'll be fixed soon.
Cockpit Machines page is not connecting to libvirt. v.321-1.fc41