Thanks, given that info it seems clear to be a kernel and not a qemu
bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: virt-manager (Ubuntu)
--
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:
New
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
