From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "\"常怀鑫(一斋)\"" <huaixin.chx@alibaba-inc.com>, keir <keir@xen.org>,
"Ian.Campbell" <Ian.Campbell@citrix.com>,
"stefano.stabellini" <stefano.stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Ian.Jackson" <Ian.Jackson@eu.citrix.com>,
"george.dunlap" <george.dunlap@eu.citrix.com>
Cc: "\"刘劲松(凯耳)\"" <jinsong.liu@alibaba-inc.com>
Subject: Re: live-migration restore failed error
Date: Mon, 15 Sep 2014 14:59:28 +0100 [thread overview]
Message-ID: <5416F0C0.4090308@citrix.com> (raw)
In-Reply-To: <983a73c3-c2db-4845-92a1-82ef8381b20a@alibaba-inc.com>
[-- Attachment #1.1: Type: text/plain, Size: 1941 bytes --]
On 15/09/2014 10:41, 常怀鑫(一斋) wrote:
> We are working on live-migration based on Xen-4.0.1(For history
> reason, and meantime we are upgrading our Xen to very latest version).
> Restore failed when live migrating ubuntu12.04 on xen-4.0.1. To be
> more specific, error occurred when populating memory. Error messages
> are as follow:
>
> [2014-09-12 22:40:40 7331 1189091648] DEBUG (XendCheckpoint:307)
> [xc_restore]: /usr/lib64/xen/bin/xc_restore 4 2763 3 4 1 1 1 0
> [2014-09-12 22:40:40 7331 1189091648] DEBUG (XendCheckpoint:428)
> Thread-40188
> [2014-09-12 22:40:40 7331 1172306240] INFO (XendCheckpoint:476)
> Thread-40188:xc_domain_restore start: p2m_size = fefff
> [2014-09-12 22:40:40 7331 1172306240] INFO (XendCheckpoint:476)
> Thread-40188:Reloading memory pages: 0%
> [2014-09-12 22:40:50 7331 1172306240] INFO (XendCheckpoint:476)
> Thread-40188:Failed allocation for dom 2763: 128 extents of order 0
> [2014-09-12 22:40:50 7331 1172306240] INFO (XendCheckpoint:476)
> Thread-40188:ERROR Internal error: Failed to allocate memory for batch.!
> [2014-09-12 22:40:50 7331 1172306240] INFO (XendCheckpoint:476)
> Thread-40188:
> [2014-09-12 22:40:50 7331 1172306240] INFO (XendCheckpoint:476)
> Thread-40188:Restore exit with rc=1
> [2014-09-12 22:40:50 7331 1189091648] DEBUG (XendCheckpoint:462)
> /usr/lib64/xen/bin/xc_restore 4 2763 3 4 1 1 1 0 failed status 256
> [2014-09-12 22:40:50 7331 1189091648] DEBUG (XendDomainInfo:3845)
> XendDomainInfo.destroy: domid=2763
>
> In this case, populate_physmap terminated with nr_done 127. So
> xc_memory_op return 127 while nr_extents equals 128.
>
> This problem happends once every 1770th live migration or so. As I am
> debugging this issue, I'm sending this email to ask for suggestions on
> this issue.
>
> Thanks,
> Huaixin Chang
Xen is unable to fulfil the allocation request. You have run out of
host memory.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 4079 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-09-15 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 9:41 live-migration restore failed error 常怀鑫(一斋)
2014-09-15 10:12 ` 答复: " 刘劲松(凯耳)
2014-09-15 13:59 ` Andrew Cooper [this message]
2014-09-15 16:15 ` 答复：live-migration " 常怀鑫(一斋)
2014-09-19 3:41 ` 常怀鑫(一斋)
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=5416F0C0.4090308@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=huaixin.chx@alibaba-inc.com \
--cc=jinsong.liu@alibaba-inc.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--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).