[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1307225] Re: Running a virtual machine on a Haswell sy
From: |
xiando |
Subject: |
[Qemu-devel] [Bug 1307225] Re: Running a virtual machine on a Haswell system produces machine check events |
Date: |
Sat, 24 May 2014 00:42:15 -0000 |
Used QEMU this morning, noticed mce error in log, searched, found this.
* model name: Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz (it's a Haswell)
* kernel 3.14.4-gentoo
* app-emulation/qemu-1.6.1
* qemu-system-i386 -enable-kvm andsoon
* [73468.545378] mce: [Hardware Error]: Machine check events logged
# mcelog
Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 0
TIME 1400824994 Fri May 23 08:03:14 2014
MCG status:
MCi status:
Corrected error
Error enabled
MCA: Internal parity error
STATUS 90000040000f0005 MCGSTATUS 0
MCGCAP c07 APICID 0 SOCKETID 0
CPUID Vendor Intel Family 6 Model 60
I don't have anything to contribute other than that Tobias is not the
only one who gets this hardware error message when using QEMU on a
Haswell.
--
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:
New
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