Displaying 3 results from an estimated 3 matches for "cpuid4a_msr_based_apic".
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
2008 Dec 29
13
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
Hi,
When dom0 is under heavy load any Vista or Windows 2008 HVM''s that are
running and have multiple cpu''s assigned often BSOD with code
0x00000101 "A clock interrupt was not recevied ona secondary
processor within the allocated time interval"
It only happens if the load in dom0 is high enough to make the mouse
pointer lagged, once the mouse fails to track in
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
2008 Dec 29
13
BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
Hi,
When dom0 is under heavy load any Vista or Windows 2008 HVM''s that are
running and have multiple cpu''s assigned often BSOD with code
0x00000101 "A clock interrupt was not recevied ona secondary
processor within the allocated time interval"
It only happens if the load in dom0 is high enough to make the mouse
pointer lagged, once the mouse fails to track in
2013 Jun 10
35
Xen 4.3 development update
There are basically three issues we''re waiting to sort out (see below
for more info):
* XSA-55
* cpu hotplug in qemu-upsream
* The MMIO hole issue
Unfortuantely, there is considerable uncertainty about how long it
will take for each of those to complete. We''re hoping to be able to
release maybe on the 19th,
This information will be mirrored on the Xen 4.3 Roadmap wiki page: