From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] `libvirt` hangs on connecting
Date: Tue, 21 Sep 2021 21:36:46 +0200 [thread overview]
Message-ID: <20210921193646.XXqs70Sf1Wz0G7XpxQEZGosGn6uJCGmhIFKUhHVpo_Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32561@inbox.vuxu.org>
[-- 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.
prev parent reply other threads:[~2021-09-21 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 1:24 [ISSUE] " 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
2021-08-27 17:20 ` ericonr
2021-09-19 12:43 ` leper
2021-09-21 19:36 ` Johnnynator [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210921193646.XXqs70Sf1Wz0G7XpxQEZGosGn6uJCGmhIFKUhHVpo_Q@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).