From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36801) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6hMv-0003rX-N3 for qemu-devel@nongnu.org; Sat, 28 May 2016 12:45:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b6hMp-00085f-LI for qemu-devel@nongnu.org; Sat, 28 May 2016 12:45:44 -0400 Received: from indium.canonical.com ([91.189.90.7]:56967) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6hMp-00085X-EO for qemu-devel@nongnu.org; Sat, 28 May 2016 12:45:39 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1b6hMo-0001yv-GC for ; Sat, 28 May 2016 16:45:38 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 71A0C2E8011 for ; Sat, 28 May 2016 16:45:38 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Sat, 28 May 2016 16:39:40 -0000 From: Gandalf-The-Red Reply-To: Bug 1580459 <1580459@bugs.launchpad.net> Sender: bounces@canonical.com References: <20160511061916.21125.98809.malonedeb@wampee.canonical.com> Message-Id: <20160528163940.22364.76820.malone@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1580459] Re: Windows (10?) guest freezes entire host on shutdown if using PCI passthrough List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I think this is what's happening to me on my windows 8.1 vm although it might be slightly different. Just about everything you guys talked about applies except I don't have to shutdown for it to freeze up in my case(although if it's on for long enough and I shut it off it freezes). It freezes up on it's own seemingly at random taking the host with it. First happened to me on a freshly installed Arch(antergos), then tried it on Debian after updating my kernel from 4.3 to 4.5(there was a bug that made the vm excruciatingly slow before 4.4) and it happened again. My hardware: i7 5820k = 8GB Ram (Upgrading to 32GB when the ram I ordered gets here) MSI X99S SLI Plus AMD Radeon R9-270X (Host GPU using "radeon" drivers) AMD Radeon HD 6950 1GB (Passthrough GPU) Interesting that aside from the GPUs(which I'm pretty sure aren't the problem) we all have very similar hardware. When I get some free time I'll try to replicate this bug on another OS but I have a feeling I'll just get the same result. I just want to see if it'll happen no matter what distro I use. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1580459 Title: Windows (10?) guest freezes entire host on shutdown if using PCI passthrough Status in QEMU: New Status in Fedora: New Bug description: Problem: after leaving a Windows VM that uses PCI passthrough (as we do for gaming graphics cards, sound cards, and in my case, a USB card) running for some amount of time between 1 and 2 hours (it's not consistent with exactly how long), and for any amount of time longer than that, shutting down that guest will, right as it finishes shutting down, freeze the host computer, making it require a hard reboot. Unbinding (or in the other user's case, unbinding and THEN binding) any PCI device in sysfs, even one that has nothing to do with the VM, also has the same effect as shutting down the VM (if the VM has been running long enough). So, it's probably an issue related to unbinding and binding PCI devices. There's a lot of info on this problem over at https://bbs.archlinux.org/v= iewtopic.php?id=3D206050 Here's a better-organized list of main details: -at least 2 confirmed victims of this bug; 2 (including me) have provided= lots of info in the link -I'm on Arch Linux and the other one is on Gentoo (distro-nonspecific) -issue affects my Windows 10 guest and others' Windows guests, but not my= Arch Linux guest (the others don't have non-Windows guests to test) -I'm using libvirt but the other user is not, so it's not an issue with l= ibvirt -It seems to be version non-specific, too. I first noticed it at, or when= testing versions still had the issue at (whichever version is lower), Linu= x 4.1 and qemu 2.4.0. It still persists in all releases of both since, incl= uding the newest ones. -I can't track down exactly what package downgrade can fix it, as downgra= ding further than Linux 4.1 and qemu 2.4.0 requires Herculean and system-de= stroying changes such as downgrading ncurses, meaning I don't know whether = it's a bug in QEMU, the Linux kernel, or some weird seemingly unrelated thi= ng. -According to the other user, "graphics intensive gameplay (GTA V) can ca= use the crash to happen sooner," as soon as "15 minutes" -Also, "bringing up a second passthrough VM with separate hardware will c= ause the same crash," and "bringing up another VM before the two-hour mark = will not result in a crash," further cementing that it's triggered by the u= n/binding of PCI devices. -This is NOT related to the very similar bug that can be worked around by= not passing through the HDMI device or sound card. Even when we removed al= l traces of any sort of sound card from the VM, it still had the same behav= ior. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1580459/+subscriptions