Cannot connect to libvirt from Virt-Manager

[Calandracas606]

Is this a new report?

Yes

System Info

Void 6.6.10_1 x86_64-musl GenuineIntel uptodate rFFFFF

Package(s) Affected

libvirt-9.10.0_1, virt-manager-4.1.0_3

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

virt-manager connects to libvirt

Actual behaviour

virt-manager shows "QEMU/KVM - Connecting..."

Steps to reproduce

1. Enable required services (dbus, libvirtd, virtlockd, virtlogd)
2. Add user to "libvirt" group
3. Sign in as user
4. Launch virt-manager

Suck on "QEMU/KVM - Connecting..."

[Calandracas606]

I've tried the fix from this issue with no success: #14721

There are many vague "libvirt isn't working on musl" issues on the internet, but its difficult to identify which ones might be relevant

[dataCobra]

Hey, could you start virt-manager from a terminal so you can see that stdout which gets produced by virt-manager?

This could be helpful to understand what might cause the connection issue.

[Calandracas606]

When I tried it again to collect logs, it mysteriously worked, despite not having changed anything for several days.

The same day that I submitted this ticked, I followed some troubleshooting as suggested on IRC.

I tried disabling the libvirtd service, and instead enabling:

• virtlockd
• virtlogd
• virtqemud
• virtstoraged
• virtnetworkd
• virtinterfaced
• virtnodedevd
• virtnwfilterd
• virtsecretd

Initially this did not work, even after several reboots.

Also tried using gnome-boxes, both the void package and flatpak, neither of them worked.

Attaching logs for future reference. virt-manager.log

Will close this ticket for now, and it appears to be working.