Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
GuiltyDoggy opened this issue Oct 10, 2024 · 4 comments

Comments

@GuiltyDoggy
Copy link

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
Copy link
Member

jelly commented Oct 10, 2024

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
Copy link
Member

garrett commented Oct 10, 2024

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

#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
Copy link
Author

It is indeed #1818. Sorry for the dupe.

Setenforce 0 fixes it for now.

@garrett
Copy link
Member

garrett commented Oct 10, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants