WARNING - OLD ARCHIVES

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

xen-devel

[Xen-devel] RE: PV resume failed after self migration failed

 
> Subject: RE: PV resume failed after self migration failed
> Date: Wed, 22 Jun 2011 14:06:18 +1000
> From: james.harper@xxxxxxxxxxxxxxxx
> To: tinnycloud@xxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx
>
> > >
> > > The xenvbd driver doesn't do any timeout, windows does the timeout
> and
> > > tells xenvbd to reset. I haven't tested the scenario you describe
> very
> > > recently, and xenvbd is now two different drivers, one for scsiport
> (<=
> > > 2003) and one for storport (>= Vista), so there could be bugs in
> either.
> > >
> >
> > The bug can be reproduced in 2003 32bit system. We are using scsi
> driver.
> > I put some log in XenVbd_HwScsiResetBus to see if there are not
> completed
> > srb(Like below)
> > but I didn't see the log when XenVbd_HwScsiResetBus called. So No IO
> is in
> > queue.
>
> Just to confirm, is this the issue that only happens when the migration
> fails in xen and is cancelled?
>
Exactly.
I've noticed some difference in log.
 
In normal resuming, from the log, we can see event port assign like below:
pdo_event_channel = 5 (Notifying event channel 5)
suspend event channel = 6
XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7  (for VBD)
XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 8  (VIF)
 
when guest resuming locally from suspend(that is migration failed in xen, guest
has already suspended, so it need resuming)
 
pdo_event_channel = 7 ( Notifying event channel 7)
suspend event channel = 8
XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 9 (vif)
 
VBD port is not allocated, since pdo is waiting fdo change.
 
It looks like port 5 and 6 is still occpuied, or pdo_event_channel bind twice?

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