cockpit-project / cockpit-machines

Cockpit UI for virtual machines
GNU Lesser General Public License v2.1
289 stars 74 forks source link

Page is stating "Virtualization service (libvirt) is not active" though it is #1854

Closed GuiltyDoggy closed 11 hours ago

GuiltyDoggy commented 12 hours ago

Cockpit Machines page is not connecting to libvirt. v.321-1.fc41

Screenshot_20241010_073108

rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● fedora:fedora/41/x86_64/kinoite
                  Version: 41.20241010.n.0 (2024-10-10T08:16:03Z)
               BaseCommit: 4458d720b56080d871e2f42fa477935e564fdee0536c769cb77cac3f039cdc7e
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
      RemovedBasePackages: firefox firefox-langpacks 131.0.2-1.fc41
          LayeredPackages: cockpit cockpit-machines cockpit-ostree cockpit-podman doas libvirt rocm-clinfo rocm-opencl rocminfo tmux vim virt-manager zsh
jelly commented 12 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.

garrett commented 11 hours ago

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.)

GuiltyDoggy commented 11 hours ago

It is indeed #1818. Sorry for the dupe.

Setenforce 0 fixes it for now.

garrett commented 11 hours ago

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.