> Attached are three logs. (I started test PV in debug mode)
>
> qemu-dm-w3.MR_cp7.vhd.log.normal:
> is the VM not crash
>
>
> qemu-dm-w3.MR_cp23.vhd.log.crash:
> is the vm crashed, but the log show a Assertion failed.
> *** Assertion failed: srb != NULL
> *** Source File:
e:\download\win-pvdrivers.hg\xenvbd\xenvbd_scsiport.c, line
> 988
> Blue screen on "NO_PAGES_AVAILABLE"
> ***STOP: 0x0000004D (0x0001566c,0x0001566c,0x00000000,0x00000000)
>
>
> qemu-dm-w3.MR_cp6.vhd.log.crash: is the vm crashed, bug no special
error in
> log
> Blue screen on "NO_PAGES_AVAILABLE"
> ***STOP: 0x0000004D (0x0001590f,0x0001590f,0x00000000,0x00000000)
>
I have checked both your bug checks. Both of them have some scsi resets
just before the crash, eg:
XenVbd --> XenVbd_HwScsiResetBus
XenVbd IRQL = 9
XenVbd <-- XenVbd_HwScsiResetBus
XenVbd --> XenVbd_HwScsiResetBus
XenVbd IRQL = 9
XenVbd <-- XenVbd_HwScsiResetBus
So I'm wondering if xenvbd is stuck. If that happened, Windows would be
able to write out to the pagefile, which is more in line with the
documentation of Bug Check 0x4D.
James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home