|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] BSOD "A clock interrupt was not recevied ona secondary proce
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 realtime the hvm's
start to bsod within a few seconds.
I have tried several versions of Xen including 3.2, 3.3 and 3.3.1 rc4,
and various kernels including the 2.6.18 xensource and 2.6.27-xen.hg.
Here is a example config from one of my vista hvms, is there a
timer/rtc setting that I need to add to avoid this problem?
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 2048
name = "Vistax86"
uuid = "b7bd2f2f-169f-4789-8aee-eaa77c543c99"
vcpus=8
vif = [ 'mac=00:16:3e:7d:bc:b1' ]
disk = [ 'phy:/dev/vg_raptor/lv_vistax86,hda,w', ',hdc:cdrom,r' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot="d"
sdl=0
vnc=1
vnclisten="127.0.0.1"
vncdisplay=11
vncpasswd='vv8176a'
stdvga=0
serial='pty'
usbdevice='tablet'
cpuid=['1:edx=xxx1xxxxxxxxxxxxxxxxxxxxxxxxxxxx,ebx=xxxxxxxx00010000xxxxxxxxxxxxxxxx','4,0:eax=001111xxxxxxxxxxxxxxxxxxxxxxxxxx']
keymap='en-gb'
Andy
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval",
Andrew Lyon <=
|
|
|
|
|