From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 196161] Kernel freezes when using AVAST under nested virtualization
Date: Tue, 08 Aug 2017 09:14:55 +0000 [thread overview]
Message-ID: <bug-196161-28872-TlC3dP3zXX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196161-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196161
--- Comment #27 from Paolo Bonzini (bonzini@gnu.org) ---
No, I cannot reproduce it. From the logs, it seems to be a deadlock between
two callers of smp_call_function, KVM and seccomp, but it's not clear what the
two are waiting (interrupts are enabled).
It's possible that a workaround is to pin QEMU's VCPU thread to one host VCPU.
If you're using libvirt, this is easily done by modifying the virtual machine's
XML.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-08-08 9:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 20:09 [Bug 196161] New: Kernel freezes by starting a kvm vm bugzilla-daemon
2017-06-22 20:11 ` [Bug 196161] " bugzilla-daemon
2017-06-22 21:53 ` bugzilla-daemon
2017-06-22 23:01 ` bugzilla-daemon
2017-06-23 22:31 ` bugzilla-daemon
2017-06-23 23:53 ` bugzilla-daemon
2017-06-23 23:55 ` bugzilla-daemon
2017-06-24 14:33 ` bugzilla-daemon
2017-06-24 15:54 ` bugzilla-daemon
2017-07-11 20:28 ` bugzilla-daemon
2017-07-20 1:12 ` bugzilla-daemon
2017-07-27 15:58 ` bugzilla-daemon
2017-07-27 16:24 ` bugzilla-daemon
2017-07-27 16:45 ` bugzilla-daemon
2017-07-27 16:46 ` bugzilla-daemon
2017-07-27 16:49 ` bugzilla-daemon
2017-07-27 16:50 ` bugzilla-daemon
2017-07-27 16:52 ` bugzilla-daemon
2017-07-27 16:52 ` bugzilla-daemon
2017-07-27 16:58 ` bugzilla-daemon
2017-07-27 16:59 ` bugzilla-daemon
2017-07-27 17:05 ` bugzilla-daemon
2017-07-27 17:13 ` bugzilla-daemon
2017-07-27 20:54 ` [Bug 196161] Kernel freezes when using AVAST under nested virtualization bugzilla-daemon
2017-07-27 20:56 ` bugzilla-daemon
2017-08-03 16:18 ` bugzilla-daemon
2017-08-07 17:38 ` bugzilla-daemon
2017-08-08 9:14 ` bugzilla-daemon [this message]
2017-08-08 16:39 ` bugzilla-daemon
2017-08-11 1:32 ` bugzilla-daemon
2017-08-15 15:48 ` bugzilla-daemon
2017-08-19 22:47 ` bugzilla-daemon
2017-08-22 1:37 ` bugzilla-daemon
2017-08-30 16:53 ` bugzilla-daemon
2017-09-03 21:34 ` bugzilla-daemon
2017-09-07 0:15 ` bugzilla-daemon
2017-09-17 17:56 ` bugzilla-daemon
2017-09-30 16:19 ` bugzilla-daemon
2017-10-26 21:31 ` bugzilla-daemon
2017-11-26 23:38 ` 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-196161-28872-TlC3dP3zXX@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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.