*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Just wanted to add that upgrading my kernel to a newer version fixed the
problem for me, too.
Host: 2x E5-2620V2, Ubuntu 14.04 LTS
Guest: 24 virtual cores, Windows Server 2008 R2
Before fix:
sudo uname -a
Linux x.contabo.net 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
Bluescreen stop 0x0000005c every few hours
After fix:
sudo uname -a
Linux x.contabo.net 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
No Bluescreens or other crashes since 7 days under full load
Upgraded with this tutorial http://askubuntu.com/questions/541775/how-
can-i-install-ubuntu-14-10s-kernel-in-ubuntu-14-04-lts
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on Windows guest (14.04 regression)
Status in QEMU:
New
Status in linux package in Ubuntu:
Confirmed
Status in qemu package in Ubuntu:
Confirmed
Bug description:
Configuring a Windows 7 guest using more than one CPU cases the guest to
fail. This happens after a few hours after guest boot. This is the error on the
blue screen:
"A clock interrupt was not received on a secondary processor within the
allocated time interval"
After resetting, the guest will never boot and a new bluescreen with
the error "STOP: 0x0000005c" appears. Shutting down the guest
completely and restarting it will allow it to boot and run for a few
hours again.
The guest was created using virt-manager. The error happens with or
without virtio devices and with both 32-bit and 64-bit Windows 7
guests.
I am using Ubuntu 14.04 release candidate.
qemu-kvm version 2.0.0~rc1+dfsg-0ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1308341/+subscriptions
