From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 204293] New: When destroying guests, hypervisor freezes for some seconds and get BUG: soft lockup - CPU* stuck for Xs
Date: Wed, 24 Jul 2019 13:02:09 +0000 [thread overview]
Message-ID: <bug-204293-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=204293
Bug ID: 204293
Summary: When destroying guests, hypervisor freezes for some
seconds and get BUG: soft lockup - CPU* stuck for Xs
Product: Virtualization
Version: unspecified
Kernel Version: 5.2.0
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: hilld@binarystorm.net
Regression: No
When destroying guests, hypervisor freezes for some seconds and get BUG: soft
lockup - CPU* stuck for Xs:
[root@zappa ~]# virsh list | grep runn | awk '{ print $1 }' | xargs -I% virsh
destroy %
Message from syslogd@zappa at Jul 24 08:56:34 ...
kernel:[5519315.215069] watchdog: BUG: soft lockup - CPU#4 stuck for 22s!
[worker:2540]
Message from syslogd@zappa at Jul 24 08:56:34 ...
kernel:watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [worker:2540]
error: Disconnected from qemu:///system due to keepalive timeout
error: Failed to destroy domain 43
error: internal error: connection closed due to keepalive timeout
Message from syslogd@zappa at Jul 24 08:57:10 ...
kernel:[5519351.240533] watchdog: BUG: soft lockup - CPU#12 stuck for 22s!
[worker:2540]
Message from syslogd@zappa at Jul 24 08:57:10 ...
kernel:watchdog: BUG: soft lockup - CPU#12 stuck for 22s! [worker:2540]
error: Failed to destroy domain 44
error: Failed to terminate process 19480 with SIGKILL: Device or resource busy
Domain 45 destroyed
Domain 46 destroyed
Domain 47 destroyed
Domain 48 destroyed
Message from syslogd@zappa at Jul 24 08:58:06 ...
kernel:[5519407.261656] watchdog: BUG: soft lockup - CPU#21 stuck for 22s!
[worker:8228]
Message from syslogd@zappa at Jul 24 08:58:06 ...
kernel:watchdog: BUG: soft lockup - CPU#21 stuck for 22s! [worker:8228]
error: Disconnected from qemu:///system due to keepalive timeout
error: Failed to destroy domain 49
error: internal error: connection closed due to keepalive timeout
Message from syslogd@zappa at Jul 24 08:59:02 ...
kernel:[5519463.135812] watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
[worker:8190]
Message from syslogd@zappa at Jul 24 08:59:02 ...
kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [worker:8190]
error: Disconnected from qemu:///system due to keepalive timeout
error: Failed to destroy domain 50
error: internal error: connection closed due to keepalive timeout
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-07-24 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 13:02 bugzilla-daemon [this message]
2023-01-27 13:06 ` [Bug 204293] When destroying guests, hypervisor freezes for some seconds and get BUG: soft lockup - CPU* stuck for Xs bugzilla-daemon
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=bug-204293-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.