[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2018-03-30 Thread Dmitrii Shcherbakov
Got similar behavior with windows server 2012r2 VMs. Environment: uname -a Linux ubuntu-q87 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ii linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1

[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2018-03-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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:

[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2018-03-30 Thread Dmitrii Shcherbakov
** 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-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2017-11-21 Thread Jimi
I just reported the bug in the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=197951 If you reported or commented on the bug here, please go comment on that report confirming as well. A lot of open-source bugzilla projects tend to rarely pay attention to bug reports that only one person has

[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2017-11-21 Thread Jimi
I have yet to try disabling swap, but in the 5 days since I downgraded the kernel to 4.12.12 from 4.12.13, I have not had a single BSOD. I think 4.12.13 is the culprit. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2017-11-21 Thread Tyler Doherty
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

[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2017-11-15 Thread Jimi
Specifically 4.12.12, because it seems that was the last version I was running before this issue started (I was on 4.12.13 when it started). I, too, can't find any other package upgrade that could have possibly been the culprit. The timing of my upgrades of any qemu or libvirt packages rule them

[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2017-11-15 Thread Jimi
I'm experiencing this BSOD issue as well. I'm also on Arch x64, and the same versions of everything (though not minimal qemu--just the normal package in the main repos). I also passthru a GPU and a USB card, but not an SSD. It will happen randomly, anytime, at least once a day, and it seems like

[Qemu-devel] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

2017-11-15 Thread adg
I've also had the exact symptoms and issues you've described. I have also noticed that the VM would BSOD with the CRITICAL_STRUCTURE_CORRUPTION message when the host system would read VM memory from swap. After disabling swap on the host system I've completely managed to eliminate this BSOD