RE: blue screen in windows balloon driver

["James Harper" <james.harper@bendigoit.com.au>]

Hold off on testing. I'm fixing up the reset code so that it does what
Windows wants. I'll post something soon if it doesn't take too long.

James

> -----Original Message-----
> From: MaoXiaoyun [mailto:tinnycloud@hotmail.com]
> Sent: Tuesday, 1 March 2011 23:34
> To: James Harper
> Cc: xen devel
> Subject: RE: blue screen in windows balloon driver
> 
> I will have new driver tested.
> Attached is the xentop snapshot.
> 
> thanks.
> 
> > Subject: RE: blue screen in windows balloon driver
> > Date: Tue, 1 Mar 2011 23:11:14 +1100
> > From: james.harper@bendigoit.com.au
> > To: tinnycloud@hotmail.com
> >
> > >
> > > exe attached, thanks.
> > >
> > > I have three machines, on each sum the *XenVbd_HwScsiResetBus*
event.
> > > 24 VMS, so
> > > grep XenVbd_HwScsiResetBus qemu-dm-w3.MR_cp* | wc -l
> > >
> > > machine 25: VM easily got crash, the sum is 200
> > > machine 23: VM never got crash, the sum is 10
> > > machine 212: VM never got crash, the sum is 16
> > >
> > > it seems that machine 25 has much more XenVbd_HwScsiResetBus event
> > > than other two machines.
> > >
> > > BTW, when start 24VM concurrently, the starting process is quite
slow,
> > takes
> > > about 20 minutes more to whole started.
> > >
> > > I commented line 505 in xenpci_pdo.c to avoid timed out.
> > >
> > > 505 //remaining -= thiswait;
> > >
> >
> > It sounds like you are overloading your disk IO bandwidth. With many
> > DomU's swapping heavily, Dom0 may simply not be able to keep up with
the
> > IO throughput required resulting in windows thinking that the scsi
> > device isn't responding. Can you check xentop and see what sort of
IO
> > operations per second you are getting?
> >
> > I have just pushed a change to dump out the in-flight scsi requests
> > (srb) when HwScsiResetBus is called. Please apply the patch and send
me
> > the next crash.
> >
> > Thanks
> >
> > James