[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "fanliang" <fanliang@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Tue, 22 Dec 2009 22:55:44 +1100
  • Cc:
  • Delivery-date: Tue, 22 Dec 2009 03:56:10 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcqCp3x8GXMChtBsQsSEqpXUiZ3v1wAVOatw
  • Thread-topic: [Xen-devel] Look for some help about Windows pv driver

> 
> Hi:
> Is there any body have used GPL Windows pv driver ? Or WLK tools ?

I've run the NDIS test a while ago (a seriously good network test
suite!) to test some of the IP offload code I'd been working on. I
haven't run much of the other stuff though.

> 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.

What version of GPLPV?

Parameter 4 of BSoD should be a pointer to a string with some more
information... can you tell me what the string contains? I assume it's
just the name of the task that crashed which won't tell us much.

> 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.

Do you know what was being tested? If it was the disk then maybe there
is some corruption happening - the WLK is supposed to give things a
pretty extreme workout so it could be touching some corner case that
we've never seen in real use. One thing I can think of is how GPLPV
behaves when allocations to system resources fail (eg memory
allocation)... if I don't know how to handle a failure at a specific
point I should have at least put an ASSERT in there so that you get a
definite crash right at the point of failure, not a strange crash some
time later, but maybe I've missed some?

If you are not running a fairly recent version of GPLPV then there was a
bug that only ever showed up under Call Of Duty 4 in server mode on one
specific map that was caused by some buffer corruption on disk
read/write.

Depending on your version of Dom0 and the version of GPLPV, there should
be debug information written out to /var/log/xen/qemu-dm-<domu
name>.log. There might be something useful in there.

If you can reproduce the problem pretty quickly, I can make a very very
new version of GPLPV available to you for testing. I haven't tested it
enough for production use yet but it would be useful to run it through
the WLK. It uses the latest WinDDK (7600).

Also, if you want the GPLPV symbol files for debugging then I have them
for any given recent release, I just don't upload them unless someone
wants them as they are big and I don't have a particularly fast link, so
just ask if you want them.

James


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.