From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34495) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9hfD-0005eZ-Ax for qemu-devel@nongnu.org; Sun, 05 Jun 2016 19:41:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b9hf8-0001gh-AV for qemu-devel@nongnu.org; Sun, 05 Jun 2016 19:41:02 -0400 Received: from indium.canonical.com ([91.189.90.7]:44565) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9hf8-0001gW-2N for qemu-devel@nongnu.org; Sun, 05 Jun 2016 19:40:58 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1b9hf5-0004MQ-8p for ; Sun, 05 Jun 2016 23:40:55 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 29DA62E80C8 for ; Sun, 5 Jun 2016 23:40:55 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Sun, 05 Jun 2016 23:34:42 -0000 From: jimrif Reply-To: Bug 1580459 <1580459@bugs.launchpad.net> Sender: bounces@canonical.com References: <20160511061916.21125.98809.malonedeb@wampee.canonical.com> Message-Id: <20160605233442.6945.56794.malone@chaenomeles.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 have been able to stop this from happening by recompiling my kernel without SND support. If you can live without sound in your host (it is still there in your guest if you pass through the sound device of your card) then try removing SND support from your hosts kernel. You can also try blacklisting the snd module and snd-hda-intel instead of removing it from your kernel if they are modules. I have not had a crash from a shutdown in a couple of months after removing SND from my hosts kernel. In my mind that points more of a finger at idea that the root of the problem has to do with binding/unbinding of the device. Chris, for your HDMI sound issue there are a couple of things that might help. I would have that issue immediately if I was using a certain virtual network card in the guest. Using virtio as your network driver helps quite a bit, however it would still mess up on me every now and again. In order to fix everything, I switched it over to MSI signalling from IRQ on the sound device in Windows 10. I also switched the graphics card driver over to MSI and have to switch them each time one of the nVidia drivers gets an update. -- = 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 libvirt: New Status in QEMU: New Status in Arch Linux: New Status in Debian: 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/libvirt/+bug/1580459/+subscriptions