All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Doherty <1728256@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64
Date: Tue, 21 Nov 2017 20:53:02 -0000	[thread overview]
Message-ID: <151129758247.18705.6495511163995730205.malone@gac.canonical.com> (raw)
In-Reply-To: 150920686502.20214.12572544661418580428.malonedeb@soybean.canonical.com

I am on Arch as well, using a customized kernel using the vfio patchset
(in this case 4.13.11). I was having the same issue as you guys, where
my Windows 10 VM with an NVIDIA card passed in was getting the
CRITICAL_STRUCTURE_CORRUPTION blue screen error message after running
for a while. Usually I saw this when hitting some form of memory (GPU or
system RAM), and it was quick (~3 hours) to crash while mining on the
GPU (as that hits the GPU memory hard).

It looks like what Jimi said above about swap seeming to be a
contributing factor seems to be correct. I have disabled swap on my host
and have seen no instability thus far.

Windows 7 also may be seeing similar issues, though it was just crashing
though without displaying an error as far as I could see. This VM has an
AMD card in it. Same goes for it, where it also has not crashed after
more than a day after disabling swap.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728256

Title:
  Memory corruption in Windows 10 guest / amd64

Status in QEMU:
  New

Bug description:
  I have a Win 10 Pro x64 guest inside a qemu/kvm running on an Arch x86_64 host. The VM has a physical GPU passed through, as well as the physical USB controllers, as well as a dedicated SSD attached via SATA; you can find the complete libvirt xml here: https://pastebin.com/U1ZAXBNg
  I built qemu from source using the qemu-minimal-git AUR package; you can find the build script here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=qemu-minimal-git (if you aren't familiar with Arch, this is essentially a bash script where build() and package() are run to build the files, and then install them into the $pkgdir to later tar them up.)

  Starting with qemu v2.10.0, Windows crashes randomly with a bluescreen
  about CRITICAL_STRUCTURE_CORRUPTION. I also tested the git heads
  f90ea7ba7c, 861cd431c9 and e822e81e35, before I went back to v2.9.0,
  which is running stable for over 50 hours right now.

  During my tests I found that locking the memory pages alleviates the
  problem somewhat, but never completely avoids it. However, with the
  crashes occuring randomly, that could as well be false conclusions; I
  had crashes within minutes after boot with that too.

  I will now start `git bisect`ing; if you have any other suggestions on
  what I could try or possible patches feel free to leave them with me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1728256/+subscriptions

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28 16:07 [Qemu-devel] [Bug 1728256] [NEW] (Regression) Memory corruption in Windows 10 guest / amd64 Wüstengecko
2017-11-05 19:36 ` [Qemu-devel] [Bug 1728256] " larsk
2017-11-06 19:36 ` Wüstengecko
2017-11-14 20:47 ` Wüstengecko
2017-11-15 14:07 ` [Qemu-devel] [Bug 1728256] " adg
2017-11-16  5:17 ` Jimi
2017-11-16  5:22 ` Jimi
2017-11-21 20:53 ` Tyler Doherty [this message]
2017-11-21 21:09 ` Jimi
2017-11-21 21:21 ` Jimi
2018-03-30 18:35 ` Dmitrii Shcherbakov
2018-03-30 18:36 ` Launchpad Bug Tracker
2018-03-30 18:53 ` Dmitrii Shcherbakov
2020-11-10  3:10 ` Thomas Huth

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=151129758247.18705.6495511163995730205.malone@gac.canonical.com \
    --to=1728256@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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.