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] Re: BSOD "A clock interrupt was not recevied ona secondary p

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval"
From: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
Date: Fri, 2 Jan 2009 18:33:48 +0000
Cc:
Delivery-date: Fri, 02 Jan 2009 10:34:32 -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:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ySgZArRehhR8n8nJ75WOEqvkug8XZlaELWS0TFspVok=; b=PY8ytKGZIEihDV/xgSORf4Um8sawa3DrAy7k70zHz2cBGTF/8rQ32E0QX96x4HjXMY L6Va+LbDiHYukqfe63GJwTnqtULoYinz4n3F7V+CLsIXJ0hmwPcN04MnONWP4Z2dgIm9 tJWLCY+MAbAnypKWAXux47iyAuHTFcapK6zgU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=oXUi8E8J40pSCZ6fxcafHRCkJRIB+6cSEBNPFRf+OAP/cPfUbsrqbeyF8tyjq2lG+K 47x4OyxdeMOaBKPFqq+pDRgjn4RVvlY5/xDsvgr0W8GZF1mGqeBu+GqsXGj/E1u+8Jlb sK8GgUk7i123Msw9zNJPaxM5ZmOC4VzzZQy5s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f4527be0812290132p2f29afe1k5dbad3888ee552ba@xxxxxxxxxxxxxx>
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>
References: <f4527be0812290132p2f29afe1k5dbad3888ee552ba@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Dec 29, 2008 at 9:32 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> 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
>

I think this is a known issue which has incorrectly been marked as
FIXED in bugzilla:

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1117

there is a second bug report of the same problem, this time with more details:

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1065

Is there a fix?

Andy

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>