From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52118) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e8StZ-00008s-Ls for qemu-devel@nongnu.org; Sat, 28 Oct 2017 11:19:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e8StW-0005NY-Gr for qemu-devel@nongnu.org; Sat, 28 Oct 2017 11:19:33 -0400 Received: from indium.canonical.com ([91.189.90.7]:38394) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e8StW-0005Mp-AF for qemu-devel@nongnu.org; Sat, 28 Oct 2017 11:19:30 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1e8StU-00051N-8p for ; Sat, 28 Oct 2017 15:19:28 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 2874B2E80CE for ; Sat, 28 Oct 2017 15:19:28 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Sat, 28 Oct 2017 15:07:17 -0000 From: Tobias-leupold <1307225@bugs.launchpad.net> Reply-To: Bug 1307225 <1307225@bugs.launchpad.net> Sender: bounces@canonical.com References: <20140413204536.17279.23843.malonedeb@chaenomeles.canonical.com> Message-Id: <150920323751.20053.15293397563192482354.malone@soybean.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1307225] Re: Running a virtual machine on a Haswell system produces machine check events List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Last time I saw this error in my mcelog was in August. Probably, some update fixed it. I'll check the next days/weeks if I still see it. This is a quite long time, at the time of my original bug report, I got the errors multiple times a day and later multiple times a week. About the workaround moving to 64 bit OS images: Well, if you're (like in my case) stuck with dinosaur OS (Windows SBS 2003), there's no way to simply move to a 64 bit image ;-) But as said: I think it simply disappeared by some update. I'm using 2.10.0 at the moment. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1307225 Title: Running a virtual machine on a Haswell system produces machine check events Status in QEMU: Incomplete Bug description: I'm running a virtual Windows SBS 2003 installation on a Xeon E3 Haswell system running Gentoo Linux. First, I used Qemu 1.5.3 (the latest stable version on Gentoo). I got a lot of machine check events ("mce: [Hardware Error]: Machine check events logged") in dmesg that always looked like (using mcelog): Hardware event. This is not a software error. MCE 0 CPU 3 BANK 0 TIME 1397455091 Mon Apr 14 07:58:11 2014 MCG status: MCi status: Corrected error Error enabled MCA: Internal parity error STATUS 90000040000f0005 MCGSTATUS 0 MCGCAP c09 APICID 6 SOCKETID 0 CPUID Vendor Intel Family 6 Model 60 I found this discussion on the vmware community: https://communities.vmware.com/thread/452344 It seems that this is (at least partly) caused by the Qemu machine. I switched to Qemu 1.7.0, the first version to use "pc-i440fx-1.7". With this version, the errors almost disappeared, but from time to time, I still get machine check events. Anyways, they so not seem to affect neither the vm, nor the host. The Haswell machine has been set up and running for several days without a single error message. They only appear when the VM is running. so I think this is actually some problem with the Haswell architecture (and not a real hardware error). To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1307225/+subscriptions