xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>,
	Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: live migration question
Date: Tue, 31 Jan 2012 12:56:37 +0000	[thread overview]
Message-ID: <CB4D9585.3894A%keir@xen.org> (raw)
In-Reply-To: <4F27E1CE.6080100@ts.fujitsu.com>

On 31/01/2012 12:42, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:

>> I've made an additional test using xm save/xm restore to see if the same
>> problem shows up. It does NOT. Mapping succeeds at once while restoring
>> memory is still running. I always thought xm restore and live migration on
>> the target machine are more or less the same. This seems not to be true.
> 
> Okay, here are my results (so far):
> 
> do_mmu_update() calls mod_l1_entry() which fails with -EINVAL due to an
> invalid mfn and p2m-type == 4 returned by:
> 
> mfn_x(gfn_to_mfn(pg_dom, l1e_get_pfn(nl1e), &p2mt))
> 
> I still don't see why xc_restore is able to do the mapping while my daemon is
> not. And I can't find any difference between a domain creation due to
> xm restore and a live migration.

Memory pages are populated as they appear in the migration data stream.
Perhaps you are trying to map a guest page that has simply not yet been
allocated.

Bear in mind that IOCTL_PRIVCMD_MMAPBATCH_V2 will note, but proceed past,
failed individual mappings. While IOCTL_PRIVCMD_MMAP, for example, will fail
the entire ioctl() in that situation. There's a reason that xc_restore uses
the former ioctl!

 -- Keir

  reply	other threads:[~2012-01-31 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 12:24 live migration question Juergen Gross
2012-01-30 16:26 ` Jan Beulich
2012-01-31  7:50   ` Juergen Gross
2012-01-31 12:42     ` Juergen Gross
2012-01-31 12:56       ` Keir Fraser [this message]
2012-01-31 13:58         ` Juergen Gross
2012-01-31 14:17           ` Keir Fraser

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=CB4D9585.3894A%keir@xen.org \
    --to=keir@xen.org \
    --cc=JBeulich@suse.com \
    --cc=juergen.gross@ts.fujitsu.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).