From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33028) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f1z2M-0001y5-6U for qemu-devel@nongnu.org; Fri, 30 Mar 2018 14:46:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f1z2J-0003xH-23 for qemu-devel@nongnu.org; Fri, 30 Mar 2018 14:46:06 -0400 Received: from indium.canonical.com ([91.189.90.7]:40446) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f1z2I-0003sk-Rp for qemu-devel@nongnu.org; Fri, 30 Mar 2018 14:46:02 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1f1z2F-0000RK-Ds for ; Fri, 30 Mar 2018 18:45:59 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 7D0832E81A6 for ; Fri, 30 Mar 2018 18:45:57 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 30 Mar 2018 18:35:54 -0000 From: Dmitrii Shcherbakov <1728256@bugs.launchpad.net> Reply-To: Bug 1728256 <1728256@bugs.launchpad.net> Sender: bounces@canonical.com References: <150920686502.20214.12572544661418580428.malonedeb@soybean.canonical.com> Message-Id: <152243495455.5421.9984939476286091194.launchpad@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- = 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 Status in linux package in Ubuntu: Confirmed 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 US= B controllers, as well as a dedicated SSD attached via SATA; you can find t= he 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/PKG= BUILD?h=3Dqemu-minimal-git (if you aren't familiar with Arch, this is essen= tially 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