From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41511) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fIVfd-0001OI-PG for qemu-devel@nongnu.org; Tue, 15 May 2018 04:50:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fIVfa-000470-Ks for qemu-devel@nongnu.org; Tue, 15 May 2018 04:50:57 -0400 Received: from indium.canonical.com ([91.189.90.7]:58536) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fIVfa-00046V-Db for qemu-devel@nongnu.org; Tue, 15 May 2018 04:50:54 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1fIVfX-0003jZ-18 for ; Tue, 15 May 2018 08:50:51 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 2836C2E8F3E for ; Tue, 15 May 2018 08:50:49 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 15 May 2018 08:42:14 -0000 From: =?utf-8?q?Fran=C3=A7ois_Guerraz?= Reply-To: Bug 1769189 <1769189@bugs.launchpad.net> Sender: bounces@canonical.com References: <152544791493.32626.6219738999075353422.malonedeb@gac.canonical.com> Message-Id: <152637373476.27515.702529592088654679.malone@chaenomeles.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1769189] Re: Issue with qemu 2.12.0 + SATA List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I have done some further tests and the problem seems to be SATA, not UEFI, I have updated the bug description to reflect this. ** Summary changed: - Issue with qemu 2.12.0 + UEFI + Issue with qemu 2.12.0 + SATA ** Description changed: - (first reported here: https://bugzilla.tianocore.org/show_bug.cgi?id=3D949 - ) + [EDIT: I first thought that OVMF was the issue, but it turns out to be + SATA] = - I had a Windows 10 VM running perfectly fine with OVMF UEFI, since I + I had a Windows 10 VM running perfectly fine with a SATA drive, since I upgraded to qemu 2.12, the guests hangs for a couple of minutes, works for a few seconds, and hangs again, etc. By "hang" I mean it doesn't freeze, but it looks like it's waiting on IO or something, I can move the mouse but everything needing disk access is unresponsive. = - What doesn't work: qemu 2.12 with OVMF - What works: using BIOS or downgrading qemu to 2.11.1. + What doesn't work: qemu 2.12 with SATA + What works: using VirIO-SCSI with qemu 2.12 or downgrading qemu to 2.11.1= and keep using SATA. = - Platform is arch linux 4.16.7 on skylake, I have attached the vm xml - file. + Platform is arch linux 4.16.7 on skylake and Haswell, I have attached + the vm xml file. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1769189 Title: Issue with qemu 2.12.0 + SATA Status in QEMU: New Bug description: [EDIT: I first thought that OVMF was the issue, but it turns out to be SATA] I had a Windows 10 VM running perfectly fine with a SATA drive, since I upgraded to qemu 2.12, the guests hangs for a couple of minutes, works for a few seconds, and hangs again, etc. By "hang" I mean it doesn't freeze, but it looks like it's waiting on IO or something, I can move the mouse but everything needing disk access is unresponsive. What doesn't work: qemu 2.12 with SATA What works: using VirIO-SCSI with qemu 2.12 or downgrading qemu to 2.11.1= and keep using SATA. Platform is arch linux 4.16.7 on skylake and Haswell, I have attached the vm xml file. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1769189/+subscriptions