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/
Home Products Support Community News


答复: [Xen-devel] Look for some help about Windows pv driver

To: 'Paul Durrant' <paul.durrant@xxxxxxxxxx>
Subject: 答复: [Xen-devel] Look for some help about Windows pv driver
From: fanliang <fanliang@xxxxxxxxxx>
Date: Tue, 22 Dec 2009 18:36:21 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Dec 2009 02:36:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B30938B.8020809@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqC6oR558EEyAXlSAmTt+YMigd4FgABvm8w
Thanks a lot. 
I can understand what you said , But what puzzled me is that I saw nothing
about my windows pv driver from the output of   !analyze -v inside windbg .I
am not sure that  the BSoD had nothing with the windows pv driver.  WLK goes
very well in other windows system without pv driver ,so I guess the pv
driver cases the BSod. 


发件人: Paul Durrant [mailto:paul.durrant@xxxxxxxxxx] 
发送时间: 2009年12月22日 17:38
收件人: fanliang
抄送: xen-devel@xxxxxxxxxxxxxxxxxxx
主题: Re: [Xen-devel] Look for some help about Windows pv driver

fanliang wrote:
> Is there any body have used GPL Windows pv driver ? Or WLK tools ? 
> After I installed GPL windows pv driver in my windows vm, I run WLK 
> for a while, and a few minutes later, I got a BSoD with error code
> STOP0X000000F4 . Used windbg to debug, I got some call stack about  
> the system proccess .It is strange that the call stack include nothing 
> about the pv driver. I'm wandering how can I fix this problem ? Many 
> thanks if some one gave me some suggestions.

First, have a look at
http://msdn.microsoft.com/en-us/library/ms789516.aspx and look up the
bugcheck code. In your case it's CRITICAL_OBJECT_TERMINATION. If you look at
http://msdn.microsoft.com/en-us/library/ms797140.aspx you'll see that
parameter 1 of the bugcheck tells you the object type (process or thread),
parameter 2 points to the object, parameter 3 points to the process image
file name and parameter 4 points to an ASCII string telling you what
If you didn't already, then run !analyze -v inside windbg as it will also
tell you most of this and decode some of the info for you.


Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom

Xen-devel mailing list