[Bug 1308341] Re: Multiple CPUs causes blue screen on Windows guest
Hein Gustavsen
1308341 at bugs.launchpad.net
Wed Apr 16 06:38:47 UTC 2014
** Description changed:
- 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:
+ 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.
+
+ I am using Ubuntu 14.04 release candidate.
+
+ qemu-kvm version 2.0.0~rc1+dfsg-0ubuntu3
** Description changed:
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.
+ without virtio devices and with both 32-bit and 64-bit Windows 7 guest.
I am using Ubuntu 14.04 release candidate.
qemu-kvm version 2.0.0~rc1+dfsg-0ubuntu3
** Description changed:
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 guest.
+ 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
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on Windows guest
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1308341/+subscriptions
More information about the Ubuntu-server-bugs
mailing list