WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] BSOD "A clock interrupt was not recevied ona secondary proce

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
From: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
Date: Mon, 29 Dec 2008 09:32:32 +0000
Delivery-date: Mon, 29 Dec 2008 01:33:10 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=caEyLRGV9bYNY7+LWTQcdFkg/w0DZGO8bRsu3N4ejVg=; b=qo3al4FlUHcvdiOnqMAQ3w6/wUNkP7HAqt83HphYaK1PLb/DVHHFe2dRfAwE80pH9c PgOqDkFvUE4KczXjkvjk5cAhdgbOZLztOIeZVIQ2MrBrBblz14INIDxn3FjsBM9M/lU8 ym1tex+zLILVt3BVr9fvqWrRTdWqP92xbE3tg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=aB9n5xR3ke+CTkheEKBRY04O622OXwHssGZ2/xMq+vvp9RT0HR4pwpP2sF7NojJ3F8 QqS2tHNaiK4lg3lc92yqzGMMraA9HYVY4LjjbUSMFienB+VmlfU5b8NjABrJiWab5Akp wCe5wfLx4WmiMzynUfJvUKJ0Px3jhSc5H5H/w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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 <=