** Changed in: qemu
Status: Incomplete => Triaged
--
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
The errors still keep appearing. The mcelog still shows the exact errors
posted in the very fist comment.
--
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
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 mov
I'm not sure if this can still be reproduces but I've found a workaround
quite a while ago. The problem disappeared once I migrated the virtual
machines using 32 bit OS images to 64 bit. The mix of 32 and 64 bit VMs
was the causing these problems at least on my server.
--
You received this bug no
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QE
Minor Update: Bug occurs under Intel Skylake, too.
System-information: Intel Core i7-6700 with 4x8 GB Samsung
M378A1G43DB0-CPB DDR4-2133 RAM, Motherboard: Fujitsu D3401-H1
Dec 15 06:53:30 srv01 kernel: [224214.850599] mce: [Hardware Error]: Machine
check events logged
Dec 15 06:55:08 srv01 kern
I'm seeing these MCE messages too.
My hardware is i7 4790K on a Gigabyte Z97X Gaming GT motherboard.
I run a mixture of Linux and Windows (client and server editions)
guests. Hipervisor is kvm. I'm seeing these MCE messages since I
virtualized a Windows Server 2008 R2 SP1. Neither Windows XP nor
mce=ignore_ce indeed "fixes" the messages. However, it will mask real
(important) errors as well.
Since Intel can't or won't correct the bug with a microcode update, how
about filtering it in the kernel?
http://svnweb.freebsd.org/base/head/sys/x86/x86/mca.c?r1=269052&r2=269051&pathrev=269052
--
Just my 2 cents. I have two Haswell boxes with Ubuntu Server 14.04 each
running bunch of VMs. The first one is Intel Core i7-4770K and it runs
only Linux VMs. There is no single MCE here for at least one year. The
second box is Intel Core i7-4790K and it runs mix of Linux and Windows
2003 VMs. MCE
I think this is related to the Haswell erratum 131 of the 'Intel® Xeon®
Processor E3-1200 v3 Product Family Specification Update' at:
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-e3-1200v3-spec-update.pdf
HSW131. Spurious Corrected Errors May be Report
So, at least, this does not seem to be something to worry about. But
anyways, why does it only happen if a virtual machine is executed?
--
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:
>From Documentation/x86/x86_64/boot-options.txt:
mce=bootlog
Enable logging of machine checks left over from booting.
Disabled by default on AMD because some BIOS leave bogus ones.
If your BIOS doesn't do that it's a good idea to enable though
to make sure you lo
Try adding this to the Linux commandline, in your bootloader:
mce=nobootlog
--
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 mach
I got a new Haswell based system a few days ago. It has been running
fine without warnings but today I started a VirtualBox VM and got a MCE
soon afterwards. "MCA: Internal parity error" like everyone else. From
reading this bug and the vmware link in the first post it seems like
this problem occur
attachment
logfiles, dmidecode, system information
** Attachment added: "logfiles, dmidecode, system information"
https://bugs.launchpad.net/qemu/+bug/1307225/+attachment/4162599/+files/logfiles-mce.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
I can confirm this.
Using qemu-kvm for three virtual machines on Ubuntu 14.04 LTS using a
Intel i7-4770 Haswell based server.
dmesg:
[63429.847437] mce: [Hardware Error]: Machine check events logged
[65996.795630] mce: [Hardware Error]: Machine check events logged
mcelog:
Hardware event. This i
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 log
Running the VM with "-cpu Haswell" set still causes those "Internal
Parity Errors", but not so many …
** Description changed:
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).
Still happens with qemu 2.0.0 and the same environment (Windows SBS 2003
32 bit guest on a Gentoo Linux amd64 Haswell host).
--
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 v
** Description changed:
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
** Description changed:
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
21 matches
Mail list logo
