From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 197951] New: QEMU/KVM & VFIO & PCI passthru with Windows 10 x64
guest: memory access intermittently causes CRITICAL_STRUCTURE_CORRUPTION BSOD
unless swap is disabled on host, since 4.12.13
Date: Tue, 21 Nov 2017 21:19:09 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: kvm@kernel.org
Return-path:
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:34882 "EHLO
mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
by vger.kernel.org with ESMTP id S1751263AbdKUVTK (ORCPT
); Tue, 21 Nov 2017 16:19:10 -0500
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 24C6729A0D
for ; Tue, 21 Nov 2017 21:19:10 +0000 (UTC)
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=197951
Bug ID: 197951
Summary: QEMU/KVM & VFIO & PCI passthru with Windows 10 x64
guest: memory access intermittently causes
CRITICAL_STRUCTURE_CORRUPTION BSOD unless swap is
disabled on host, since 4.12.13
Product: Virtualization
Version: unspecified
Kernel Version: 4.12.13
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: JimiJames.Bove@gmail.com
Regression: No
Originally reported here: https://bugs.launchpad.net/qemu/+bug/1728256
The title explains it all. When running a Windows 10 x64 guest that passes
through a PCIe device with VFIO (especially a GPU, or perhaps only if at least
one passed device is a GPU, since nobody who isn't passing through a GPU has
confirmed this) on kernel version 4.12.13 and up, the guest will crash with the
CRITICAL_STRUCTURE_CORRUPTION blue screen of death randomly when accessing the
host's memory. You have to be doing something memory intensive, like mining or
gaming, for it to happen often enough to really notice, but if you do, it
happens once an hour or every few hours.
I downgraded to 4.12.12 and the issue went away. Others disabled swap instead
of downgrading, and the issue went away. Disabling swap isn't an option for me,
so I can't upgrade the kernel until this is fixed.
--
You are receiving this mail because:
You are watching the assignee of the bug.