From: Wei Liu <wei.liu2@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: "Cendrin Sa" <cendrinoe@gmail.com>,
"Wei Liu" <Wei.Liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: Save/Restore is not working properly
Date: Thu, 11 Aug 2016 16:18:13 +0100 [thread overview]
Message-ID: <20160811151813.GQ20641@citrix.com> (raw)
In-Reply-To: <CAFLBxZacoQn=whDb644vJNQ18pscfgTWZVsaaGAf+45gQUQ-yg@mail.gmail.com>
On Wed, Aug 10, 2016 at 02:24:09PM +0100, George Dunlap wrote:
> On Wed, Aug 10, 2016 at 12:11 PM, Roger Pau Monné <roger.pau@citrix.com> wrote:
> > On Sun, Aug 07, 2016 at 07:51:14PM +0430, Cendrin Sa wrote:
> >> Hi,
> >> I was searching a way to clone a machine using both memory and disk
> >> approach.
> >> I checked xen save/restore but after restoring, I can only work some
> >> seconds with my machine and it will crash with the_kernel_task_hang_up.
> >> using an script* to clone a machine is not working either.
> >> so is it a bug or something or I'm cloning the wrong way?
> >
> > Hello,
> >
> > I've not tried to perform cloning myself, but I have a little script to
> > perform VM checkpoints (so that you can restore the VM to any given point in
> > time). It's based on FreeBSD so it uses ZFS, but it should work with LVM
> > also if you replace it with the appropriate runes. AFAICT it should be quite
> > easy to expand it to also do VM cloning. This is transparent from a VM point
> > of view.
>
> FWIW on a recent version of Xen-unstable, "xl save -c" appears to be
> broken, at least with me CentOS 6 VM. If I do "xl save" then "xl
> restore", everything works fine; but if I do "xl save -c", then the
> save appears to work as normal, and after it's done the guest console
> has output similar to the output it has when restoring, but processes
> which access the disk hang, and in 2 minutes I get "hung process"
> output as Cendrin described.
>
> I do get some warning messages though:
>
> Using NULL legacy PIC
> WARNING: g.e. still in use!
> WARNING: leaking g.e. and page still in use!
> WARNING: g.e. still in use!
> WARNING: leaking g.e. and page still in use!
> WARNING: g.e. still in use!
> WARNING: leaking g.e. and page still in use!
> Changing capacity of (202, 0) to 4194288 sectors
>
> This is the stock CentOS 6.6 kernel: 2.6.32-504.16.2.el6.x86_64
>
It looks like the guest kernel is trying to free up all the grant
references.
In the case of xl save -c my impression is that it shouldn't be doing
that because the suspend is supposed to be canceled from guest's PoV.
See comment in xenctrl.h for xc_domain_resume.
Also related: 8903a7a5f6a47cc40c1c204a1cc28b0030b04486
Wei.
> -George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-11 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 15:21 Save/Restore is not working properly Cendrin Sa
2016-08-07 17:23 ` Cendrin Sa
2016-08-10 9:31 ` George Dunlap
2016-08-10 11:11 ` Roger Pau Monné
2016-08-10 13:24 ` George Dunlap
2016-08-11 15:18 ` Wei Liu [this message]
2016-08-13 6:34 ` Cendrin Sa
2016-08-13 6:40 ` Cendrin Sa
2016-08-19 16:15 ` Cendrin Sa
2016-08-24 10:50 ` Wei Liu
2016-08-24 11:08 ` Roger Pau Monné
2016-08-29 10:27 ` Cendrin Sa
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=20160811151813.GQ20641@citrix.com \
--to=wei.liu2@citrix.com \
--cc=cendrinoe@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).