From: "Liu.yi" <liu.yi24@zte.com.cn>
To: xen-devel@lists.xensource.com
Subject: Re: xm save -c problem
Date: Sun, 16 Dec 2012 03:26:37 -0800 (PST) [thread overview]
Message-ID: <1355657197024-5713084.post@n5.nabble.com> (raw)
In-Reply-To: <1355650190976-5713082.post@n5.nabble.com>
Unfortunately xm restore failed because when vm restores(resume)
xpdd->pdo_event_channel and xpdd->suspend_evtchn aren't 0.
EvtChn_Unbind and EvtChn_Close pdo_event_channel in EvtChn_Init when
xpdd->pdo_event_channel isn't 0;
EvtChn_Unbind and EvtChn_Close suspend_evtchn in
XenPci_ConnectSuspendEvt when xpdd->suspend_evtchn isn't 0;
After modifing pv driver as above, xm save -c and xm restore seems work
fine. Again, I'm not sure about these.
--
View this message in context: http://xen.1045712.n5.nabble.com/xm-save-c-problem-tp5713082p5713084.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-12-16 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 9:29 xm save -c problem Liu.yi
2012-12-16 11:26 ` Liu.yi [this message]
2012-12-16 12:46 ` xm save -c problem with GPLPV drivers and winxp Pasi Kärkkäinen
2012-12-17 21:23 ` Konrad Rzeszutek Wilk
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=1355657197024-5713084.post@n5.nabble.com \
--to=liu.yi24@zte.com.cn \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).