From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 198205] infinite loop in vmx_vcpu_run on x86_64
Date: Sun, 07 Jan 2018 13:54:51 +0000
Message-ID: <bug-198205-28872-hbpOE3ve9D@https.bugzilla.kernel.org/>
References: <bug-198205-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: kvm@kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:60828 "EHLO
        mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1753945AbeAGNyw (ORCPT
        <rfc822;kvm@vger.kernel.org>); Sun, 7 Jan 2018 08:54:52 -0500
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
        by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 349FD288E0
        for <kvm@vger.kernel.org>; Sun,  7 Jan 2018 13:54:52 +0000 (UTC)
In-Reply-To: <bug-198205-28872@https.bugzilla.kernel.org/>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

https://bugzilla.kernel.org/show_bug.cgi?id=198205

--- Comment #2 from Mark Mielke (mark.mielke@gmail.com) ---
I believe I have the same symptoms as you.

I run 4 virtual machines on a desktop Intel i7-4790K (Haswell) that acts as my
server at home. After upgrading from Fedora 26 to Fedora 27, I started to
encounter symptoms like:

1) When the host was under load, and the otherwise idle guests were woken up
(SSH, yes that has been a trigger for me too, but sometimes just virt-top and
the act of observing seemed to do it?)

2) Often when one was affected, one or more of the other three would follow in
succession, usually when they are woken up as well.

3) The guests get locked up solid. I couldn't get a kernel backtrace in the
guests and I don't know how to send a sysrq key through virt-manager or
virt-viewer to confirm.

I think I can make it happen easily within a minutes on Linux 4.13, Linux
4.14., and Linux 4.15rc6 (just tried 4.15rc6 last night, and it still happens).
I was not able to get a kernel backtrace. I also tried QEMU 2.9.1, QEMU 2.10.1,
and QEMU 2.11.0.

I have reverted to Linux 4.12.14, and I have been unable to make any of the
guests lock up so far. I had previously had a stable setup with Linux 4.12.14
and QEMU 2.9.1. We'll see if it continues to stay stable with Linux 4.12.14 and
QEMU 2.11.0.

Please let me know what I can do to help identify the cause of this problem and
get it fixed. Thank you.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.