From: Frank van der Linden <Frank.Vanderlinden@Sun.COM>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
Steve Prochniak <sprochniak@virtualiron.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Steven Smith <steven.smith@eu.citrix.com>,
xen-users@lists.xensource.com,
Ben Guthro <bguthro@virtualiron.com>
Subject: Re: Re: BSOD "A clock interrupt was not recevied onasecondary processor within the allocated time interval"
Date: Wed, 07 Jan 2009 13:48:30 -0700 [thread overview]
Message-ID: <4965151E.5050209@Sun.COM> (raw)
In-Reply-To: <f4527be0901071133w57842858ua8601b379746ef76@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
Andrew Lyon wrote:
> How do you introduce the delay? I'd like to try xen-unstable with
> viridian=1 but I want to be absolutely sure that the issue is fixed so
> if you have a patch for qemu-dm I'd appreciate it if you could post
> it, the BSOD 101 issue causes serious problems for me because I am
> using pci passthrough, I've found if the domain using passthru
> crashes, I issue "xm pci-detach", or "xm destroy" a domain that is
> using a passthru pci device, will cause the entire machine to lockup ,
> I've tried Xen 3.2.1/2/3 and 3.3.0/1 with various different kernels
> but it always happens, so if my Vista or 2008 domains that are using
> pci passthru usb2 cards BSOD at all it takes down the entire box,
> usually resulting in data loss :(
>
> Perhaps that problem might be fixed in unstable too, I will try it
> tomorrow but it would really help to have a way to trigger a bsod 101.
I use the attached change to qemu. In cpu_handle_ioreq, if send_vcpu !=
0,, it checks for the presence of a file called /tmp/qemu_delay. If it
exists, it opens it and reads a delay value from it. Then it sleeps for
that duration (in microseconds).
What I do is boot windows 2008, then open an editor to edit
/tmp/qemu_delay. From the editor, I write various values to it. An easy
way to trigger the issue is to write a large value (say, 8000000 for 8
seconds), wait a little while, and then write 0 to make the domain come
back to life. It should bluescreen at this point. Sometimes the
procedure has to be repeated a few times.
If you want to do "echo $value > /tmp/qemu_delay", you'll need to change
the hack to re-open the file each time, probably.
- Frank
[-- Attachment #2: qemu-delay.patch --]
[-- Type: text/plain, Size: 957 bytes --]
*** target-i386-dm/helper2.c.orig Wed Jan 7 12:37:30 2009
--- target-i386-dm/helper2.c Mon Dec 22 16:09:55 2008
***************
*** 47,52 ****
--- 47,54 ----
#include <limits.h>
#include <fcntl.h>
+ #include <unistd.h>
+
#include <xenctrl.h>
#include <xen/hvm/ioreq.h>
***************
*** 570,575 ****
--- 572,580 ----
extern int shutdown_requested;
CPUState *env = opaque;
ioreq_t *req = cpu_get_ioreq();
+ static int fd = -1;
+ char buf[16];
+ useconds_t udelay;
handle_buffered_io(env);
if (req) {
***************
*** 606,611 ****
--- 611,625 ----
}
req->state = STATE_IORESP_READY;
+ if (send_vcpu != 0) {
+ if (fd == -1)
+ fd = open("/tmp/qemu_delay", O_RDONLY);
+ if (fd >= 0) {
+ pread(fd, buf, sizeof buf, 0L);
+ udelay = atoi(buf);
+ usleep(udelay);
+ }
+ }
xc_evtchn_notify(xce_handle, ioreq_local_port[send_vcpu]);
}
}
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-01-07 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f4527be0812290132p2f29afe1k5dbad3888ee552ba@mail.gmail.com>
2009-01-02 18:33 ` BSOD "A clock interrupt was not recevied ona secondary processor within the allocated time interval" Andrew Lyon
[not found] ` <B99564216C25704085A82B41C46DD342088343FA@exchange.katana.local>
2009-01-05 20:24 ` Re: BSOD "A clock interrupt was not recevied onasecondary " Andrew Lyon
2009-01-05 20:55 ` Steve Prochniak
2009-01-05 21:32 ` Ben Guthro
2009-01-05 21:51 ` Keir Fraser
2009-01-06 9:34 ` Andrew Lyon
2009-01-06 9:44 ` Keir Fraser
2009-01-06 10:39 ` Steven Smith
2009-01-06 12:13 ` Ben Guthro
2009-01-07 17:42 ` Frank van der Linden
2009-01-07 19:33 ` [Xen-devel] " Andrew Lyon
2009-01-07 20:48 ` Frank van der Linden [this message]
2009-01-05 22:07 ` Andrew Lyon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4965151E.5050209@Sun.COM \
--to=frank.vanderlinden@sun.com \
--cc=andrew.lyon@gmail.com \
--cc=bguthro@virtualiron.com \
--cc=keir.fraser@eu.citrix.com \
--cc=sprochniak@virtualiron.com \
--cc=steven.smith@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.