From: MaoXiaoyun <tinnycloud@hotmail.com>
To: james.harper@bendigoit.com.au, xen devel <xen-devel@lists.xensource.com>
Subject: RE: PV resume failed after self migration failed
Date: Wed, 22 Jun 2011 13:21:13 +0800 [thread overview]
Message-ID: <BLU157-w56E447A5A99A3C7AA5B572DA500@phx.gbl> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01D57C34@trantor>
[-- Attachment #1.1: Type: text/plain, Size: 1666 bytes --]
> Subject: RE: PV resume failed after self migration failed
> Date: Wed, 22 Jun 2011 14:06:18 +1000
> From: james.harper@bendigoit.com.au
> To: tinnycloud@hotmail.com; xen-devel@lists.xensource.com
>
> > >
> > > 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
>
[-- Attachment #1.2: Type: text/html, Size: 2398 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-06-22 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY0-MC4-F15zXiPuZe00229bef@bay0-mc4-f15.Bay0.hotmail.com>
2011-06-15 12:05 ` Win2003R2 64 suspend failed in self live migration MaoXiaoyun
2011-06-15 12:21 ` James Harper
2011-06-15 23:20 ` James Harper
2011-06-16 10:28 ` MaoXiaoyun
2011-06-16 14:24 ` PV resume failed after self migration failed MaoXiaoyun
2011-06-17 1:34 ` James Harper
2011-06-19 16:46 ` MaoXiaoyun
2011-06-19 23:11 ` James Harper
2011-06-21 12:13 ` MaoXiaoyun
2011-06-22 4:06 ` James Harper
2011-06-22 5:21 ` MaoXiaoyun [this message]
2011-06-22 5:58 ` MaoXiaoyun
2011-06-24 10:32 ` MaoXiaoyun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU157-w56E447A5A99A3C7AA5B572DA500@phx.gbl \
--to=tinnycloud@hotmail.com \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.