search for: onasecondari

Displaying 5 results from an estimated 5 matches for "onasecondari".

Did you mean: onasecondary
2009 Mar 31
1
Bug#522060: xen-hypervisor-3.2-1-amd64: xen hvm Windows Bluescreen - clock interrupt was not recevied onasecondary processor within the allocated time interval
Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important Tags: patch Hi, I'm having troubles with windows 2008 server with HVM on XEN. When I allocate more than one CPU to the Windows VM, windows crashes after a few minutes with a BSOD. Other people have this problem, too. The Exact error message (BSOD) is: (the unique lines) A clock interrupt was not received on a
2009 Jan 06
0
Re: RE: Re: BSOD "A clock interrupt was not recevied onasecondary processor within the allocated time interval"
yes, the cause of BSOD 0x101 is that watchdog time interrupt was not received by the vcpu in a certain timeout in Windows kernel . this is taken place especially in vista kernel. Generally speaking, we have some ways to fix this, one is that we an write a programme whitch can intercept the trigger of BSOD 0x101, on the other word, we make kernel don''t care the watchdog time interrrupt.
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
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 Aug 15
0
Processed: closing 522060
Processing commands for control at bugs.debian.org: > close 522060 Bug #522060 [src:xen] xen-hypervisor-3.2-1-amd64: xen hvm Windows Bluescreen - clock interrupt was not recevied onasecondary processor within the allocated time interval Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 522060: