* Re: `libvirt` hangs on connecting
2021-08-18 1:24 [ISSUE] `libvirt` hangs on connecting sisungo
@ 2021-08-18 17:21 ` paper42
2021-08-18 21:50 ` sisungo
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: paper42 @ 2021-08-18 17:21 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/32561#issuecomment-901291612
Comment:
I can not reproduce this.
* were you following the handbook? https://docs.voidlinux.org/config/containers-and-vms/libvirt.html
* are all required services running? dbus, libvirtd, virtlogd, virtlockd
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: `libvirt` hangs on connecting
2021-08-18 1:24 [ISSUE] `libvirt` hangs on connecting sisungo
2021-08-18 17:21 ` paper42
@ 2021-08-18 21:50 ` sisungo
2021-08-27 14:48 ` Johnnynator
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: sisungo @ 2021-08-18 21:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
New comment by sisungo on void-packages repository
https://github.com/void-linux/void-packages/issues/32561#issuecomment-901453098
Comment:
- Yes. I was following.
- All required services are running.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: `libvirt` hangs on connecting
2021-08-18 1:24 [ISSUE] `libvirt` hangs on connecting sisungo
2021-08-18 17:21 ` paper42
2021-08-18 21:50 ` sisungo
@ 2021-08-27 14:48 ` Johnnynator
2021-08-27 16:52 ` Johnnynator
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Johnnynator @ 2021-08-27 14:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/32561#issuecomment-907258857
Comment:
Can reproduce.
Work around for now is, to enable debug logging for libvirt.
Put e.g. the following lines into /etc/libvirt/libvirt.conf
```
log_filters="3:qemu 1:libvirt 4:object 4:json 3:event 3:util"
log_outputs="3:syslog:libvirtd 1:file:/dev/null"
```
```
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: `libvirt` hangs on connecting
2021-08-18 1:24 [ISSUE] `libvirt` hangs on connecting sisungo
` (2 preceding siblings ...)
2021-08-27 14:48 ` Johnnynator
@ 2021-08-27 16:52 ` Johnnynator
2021-08-27 17:20 ` ericonr
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Johnnynator @ 2021-08-27 16:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/32561#issuecomment-907258857
Comment:
Can reproduce.
Work around for now is, to enable debug logging for libvirt.
Put e.g. the following lines into /etc/libvirt/libvirt.conf
```
log_filters="3:qemu 1:libvirt 4:object 4:json 3:event 3:util"
log_outputs="3:syslog:libvirtd 1:file:/dev/null"
```
Edit: kinda as expected, libvirtd hangs in malloc (smth, smth don't call malloc after fork in a multi threaded programm)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: `libvirt` hangs on connecting
2021-08-18 1:24 [ISSUE] `libvirt` hangs on connecting sisungo
` (3 preceding siblings ...)
2021-08-27 16:52 ` Johnnynator
@ 2021-08-27 17:20 ` ericonr
2021-09-19 12:43 ` leper
2021-09-21 19:36 ` [ISSUE] [CLOSED] " Johnnynator
6 siblings, 0 replies; 8+ messages in thread
From: ericonr @ 2021-08-27 17:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/32561#issuecomment-907354912
Comment:
This should have been fixed in https://github.com/void-linux/void-packages/commit/e17f291d75190db025128bb7a96d2cd0c7926063 , shouldn't it?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: `libvirt` hangs on connecting
2021-08-18 1:24 [ISSUE] `libvirt` hangs on connecting sisungo
` (4 preceding siblings ...)
2021-08-27 17:20 ` ericonr
@ 2021-09-19 12:43 ` leper
2021-09-21 19:36 ` [ISSUE] [CLOSED] " Johnnynator
6 siblings, 0 replies; 8+ messages in thread
From: leper @ 2021-09-19 12:43 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
New comment by leper on void-packages repository
https://github.com/void-linux/void-packages/issues/32561#issuecomment-922468032
Comment:
@ericonr it was, but that patch was removed in 4fc633808bf814d5a3874304da6840e7c9cb242. However I can verify that #32727 fixes the issue for me.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ISSUE] [CLOSED] `libvirt` hangs on connecting
2021-08-18 1:24 [ISSUE] `libvirt` hangs on connecting sisungo
` (5 preceding siblings ...)
2021-09-19 12:43 ` leper
@ 2021-09-21 19:36 ` Johnnynator
6 siblings, 0 replies; 8+ messages in thread
From: Johnnynator @ 2021-09-21 19:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Closed issue by sisungo on void-packages repository
https://github.com/void-linux/void-packages/issues/32561
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.13.10_1 x86_64-musl GenuineIntel uptodate FF
* package:
*affected package(s) including the version*: `libvirt-7.6.0_1`
### Expected behavior
Tools using `libvirt` can connect to the daemon well
### Actual behavior
All tools hangs on connecting to `qemu:///system`. `virt-manager`'s status is always `QEMU/KVM -- Connecting`, and `virsh -c qemu:///system` hangs without output. (last syscall: `poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1`)
### Steps to reproduce the behavior
1. Enable services: `libvirtd`, `virtlogd` and `virtlockd`.
2. Execute `virsh -c qemu:///system` or `virt-manager`
3. They hangs.
^ permalink raw reply [flat|nested] 8+ messages in thread