From: Juergen Gross <jgross@suse.com>
To: Stefan Bader <stefan.bader@canonical.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen-4.7
Date: Thu, 25 Aug 2016 19:31:52 +0200 [thread overview]
Message-ID: <89f98783-e657-471b-6000-2ef79abd1690@suse.com> (raw)
In-Reply-To: <9073e76c-9860-51b9-8e9d-fce6133463b2@canonical.com>
On 25/08/16 17:48, Stefan Bader wrote:
> When I try to save a PV guest with 4G of memory using xen-4.7 I get the
> following error:
>
> II: Guest memory 4096 MB
> II: Saving guest state to file...
> Saving to /tmp/pvguest.save new xl format (info 0x3/0x0/1131)
> xc: info: Saving domain 23, type x86 PV
> xc: error: Bad mfn in p2m_frame_list[0]: Internal error
So the first mfn of the memory containing the p2m information is bogus.
Weird.
> xc: error: mfn 0x4eb1c8, max 0x820000: Internal error
> xc: error: m2p[0x4eb1c8] = 0xff7c8, max_pfn 0xbffff: Internal error
> xc: error: Save failed (34 = Numerical result out of range): Internal error
> libxl: error: libxl_stream_write.c:355:libxl__xc_domain_save_done: saving
> domain: domain did not respond to suspend request: Numerical result out of range
> Failed to save domain, resuming domain
> xc: error: Dom 23 not suspended: (shutdown 0, reason 255): Internal error
> libxl: error: libxl_dom_suspend.c:460:libxl__domain_resume: xc_domain_resume
> failed for domain 23: Invalid argument
> EE: Guest not off after save!
> FAIL
>
> From dmesg inside the guest:
> [ 0.000000] e820: last_pfn = 0x100000 max_arch_pfn = 0x400000000
>
> Somehow I am slightly suspicious about
>
> commit 91e204d37f44913913776d0a89279721694f8b32
> libxc: try to find last used pfn when migrating
>
> since that seems to potentially lower ctx->x86_pv.max_pfn which is checked
> against in mfn_in_pseudophysmap(). Is that a known problem?
> With xen-4.6 and the same dom0/guest kernel version combination this does work.
Can you please share some more information? Especially:
- guest kernel version?
- any patches in kernel not being upstream, especially in Xen-specific
boot path?
- dmesg from guest with E820 map?
- guest configuration?
The same error would occur when trying to live migrate the guest. And
this has been tested a lot since above commit, so I suspect something
is very special in your case.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-25 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:48 xen-4.7 Stefan Bader
2016-08-25 16:06 ` xen-4.7 regression when saving a PV guest Stefan Bader
2016-08-25 17:31 ` Juergen Gross [this message]
2016-08-26 10:52 ` xen-4.7 regression when saving a pv guest Stefan Bader
2016-08-26 11:53 ` Juergen Gross
2016-08-26 12:11 ` Ian Jackson
2016-08-26 12:23 ` Juergen Gross
2016-08-26 12:55 ` Stefan Bader
2016-08-26 13:07 ` Wei Liu
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=89f98783-e657-471b-6000-2ef79abd1690@suse.com \
--to=jgross@suse.com \
--cc=stefan.bader@canonical.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 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.