public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@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	[thread overview]
Message-ID: <bug-197951-28872@https.bugzilla.kernel.org/> (raw)

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.

             reply	other threads:[~2017-11-21 21:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 21:19 bugzilla-daemon [this message]
2017-11-21 21:23 ` [Bug 197951] 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 bugzilla-daemon
2017-11-21 21:32 ` bugzilla-daemon
2017-11-21 21:45 ` bugzilla-daemon
2017-11-30  9:41 ` bugzilla-daemon
2017-11-30 17:45 ` bugzilla-daemon
2017-12-04  8:49 ` bugzilla-daemon
2017-12-04  9:49 ` bugzilla-daemon
2017-12-04 11:58 ` bugzilla-daemon
2017-12-04 12:32 ` bugzilla-daemon
2017-12-04 13:42 ` bugzilla-daemon
2017-12-04 19:28 ` bugzilla-daemon
2017-12-05  5:52 ` bugzilla-daemon
2017-12-05  8:15 ` bugzilla-daemon
2017-12-05  9:22 ` bugzilla-daemon
2017-12-05 10:04 ` bugzilla-daemon
2017-12-14  7:57 ` 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-197951-28872@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox