From: sirn <sirn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libvirt: fix deadlock for musl
Date: Sun, 08 Nov 2020 11:36:56 +0100 [thread overview]
Message-ID: <20201108103656.2eh-BRpLhFy4I30n1hoyAipmsbHaYKCAq49oOB2Vm8g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25905@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
New comment by sirn on void-packages repository
https://github.com/void-linux/void-packages/pull/25905#issuecomment-723558586
Comment:
Unfortunately 6.9.0 doesn't fix the issue for me. Steps to reproduce:
1. Install libvirtd-6.9.0_1 and enable as runit service
1. Restart libvirtd: `sv restart libvirtd` (or reboot)
1. Connect to libvirt: `virsh -c qemu:///system list`
1. `virsh` hangs since libvirt is in deadlock
To remedy this, I have to kill all libvirtd process except the one listed in `/var/run/libvirtd.pid` then libvirt would start working until libvirtd is restarted.
User session (qemu:///session) doesn't seems to be affected, though.
-----
Here's asciinema demostrating the issue:
https://asciinema.org/a/HThAMInYCRc8rMIVQ9P00erZC
- 0:33 virsh hangs
- 0:53 deadlock process killed; <1> tab changing from "virsh" to "oksh" right after
- 1:01 subsequent run works
Here's asciinema after the patch (without virsh hanging):
https://asciinema.org/a/28yEfP68YCcXKvKc4DHUeCy8E
next prev parent reply other threads:[~2020-11-08 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 22:45 [PR PATCH] " sirn
2020-10-26 22:52 ` [PR PATCH] [Updated] " sirn
2020-11-06 17:33 ` ahesford
2020-11-08 10:27 ` [PR PATCH] [Updated] " sirn
2020-11-08 10:36 ` sirn [this message]
2020-11-17 20:38 ` Logarithmus
2020-11-17 20:38 ` Logarithmus
2020-11-17 20:40 ` Logarithmus
2020-12-23 17:35 ` gch1p
2021-01-02 3:41 ` [PR PATCH] [Closed]: " ahesford
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=20201108103656.2eh-BRpLhFy4I30n1hoyAipmsbHaYKCAq49oOB2Vm8g@z \
--to=sirn@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).