Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Cannot connect to libvirt from Virt-Manager
@ 2024-01-08 19:36 Calandracas606
  2024-01-08 19:38 ` Calandracas606
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: Calandracas606 @ 2024-01-08 19:36 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

New issue by Calandracas606 on void-packages repository

https://github.com/void-linux/void-packages/issues/48133

Description:
### 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..."

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Cannot connect to libvirt from Virt-Manager
  2024-01-08 19:36 [ISSUE] Cannot connect to libvirt from Virt-Manager Calandracas606
@ 2024-01-08 19:38 ` Calandracas606
  2024-01-13  9:49 ` dataCobra
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: Calandracas606 @ 2024-01-08 19:38 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

New comment by Calandracas606 on void-packages repository

https://github.com/void-linux/void-packages/issues/48133#issuecomment-1881709311

Comment:
I've tried the fix from this issue with no success: https://github.com/void-linux/void-packages/issues/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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Cannot connect to libvirt from Virt-Manager
  2024-01-08 19:36 [ISSUE] Cannot connect to libvirt from Virt-Manager Calandracas606
  2024-01-08 19:38 ` Calandracas606
@ 2024-01-13  9:49 ` dataCobra
  2024-01-13 17:01 ` [ISSUE] [CLOSED] " Calandracas606
  2024-01-13 17:01 ` Calandracas606
  3 siblings, 0 replies; 5+ messages in thread
From: dataCobra @ 2024-01-13  9:49 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 337 bytes --]

New comment by dataCobra on void-packages repository

https://github.com/void-linux/void-packages/issues/48133#issuecomment-1890398152

Comment:
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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ISSUE] [CLOSED] Cannot connect to libvirt from Virt-Manager
  2024-01-08 19:36 [ISSUE] Cannot connect to libvirt from Virt-Manager Calandracas606
  2024-01-08 19:38 ` Calandracas606
  2024-01-13  9:49 ` dataCobra
@ 2024-01-13 17:01 ` Calandracas606
  2024-01-13 17:01 ` Calandracas606
  3 siblings, 0 replies; 5+ messages in thread
From: Calandracas606 @ 2024-01-13 17:01 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

Closed issue by Calandracas606 on void-packages repository

https://github.com/void-linux/void-packages/issues/48133

Description:
### 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..."

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Cannot connect to libvirt from Virt-Manager
  2024-01-08 19:36 [ISSUE] Cannot connect to libvirt from Virt-Manager Calandracas606
                   ` (2 preceding siblings ...)
  2024-01-13 17:01 ` [ISSUE] [CLOSED] " Calandracas606
@ 2024-01-13 17:01 ` Calandracas606
  3 siblings, 0 replies; 5+ messages in thread
From: Calandracas606 @ 2024-01-13 17:01 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

New comment by Calandracas606 on void-packages repository

https://github.com/void-linux/void-packages/issues/48133#issuecomment-1890593527

Comment:
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](https://github.com/void-linux/void-packages/files/13928917/virt-manager.log)

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2024-01-13 17:01 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-08 19:36 [ISSUE] Cannot connect to libvirt from Virt-Manager Calandracas606
2024-01-08 19:38 ` Calandracas606
2024-01-13  9:49 ` dataCobra
2024-01-13 17:01 ` [ISSUE] [CLOSED] " Calandracas606
2024-01-13 17:01 ` Calandracas606

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).