From: David Vrabel <david.vrabel@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel List <xen-devel@lists.xen.org>
Cc: Juergen Gross <JGross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>, Tim Deegan <tim@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Shriram Rajagopalan <rshriram@cs.ubc.ca>,
Hongyang Yang <yanghy@cn.fujitsu.com>
Subject: Re: Buggy interaction of live migration and p2m updates
Date: Mon, 1 Dec 2014 14:38:23 +0000 [thread overview]
Message-ID: <547C7D5F.3090009@citrix.com> (raw)
In-Reply-To: <546E32BB.8090909@citrix.com>
On 20/11/14 18:28, Andrew Cooper wrote:
>
> 1) Freeze the guests p2m during live migrate
> 2) Deep p2m dirty tracking
> 3) Eagerly check for p2m structure changes.
> 4) Request p2m structure change updates from the guest
> Proposed solution: A combination of 2, 3 and 4.
Option 5: don't change anything. PV guests and toolstacks are
well-behaved and ensure that p2m updates do not occur during domain save.
We have never supported migrating non-cooperative PV guests.
I'd be more interested fixing this for HVM guests.
David
next prev parent reply other threads:[~2014-12-01 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 18:28 Buggy interaction of live migration and p2m updates Andrew Cooper
2014-11-21 5:41 ` Juergen Gross
2014-11-21 10:32 ` Andrew Cooper
2014-11-27 15:14 ` Tim Deegan
2014-11-21 9:43 ` Ian Campbell
2014-11-21 10:24 ` Andrew Cooper
2014-11-21 10:46 ` Ian Campbell
2014-11-21 11:07 ` Andrew Cooper
2014-11-21 11:15 ` Ian Campbell
2014-11-21 11:20 ` Juergen Gross
2014-11-21 11:24 ` Ian Campbell
2014-11-21 12:15 ` Jan Beulich
2014-11-21 12:20 ` Jürgen Groß
2014-11-21 10:43 ` Jan Beulich
2014-11-21 10:54 ` Andrew Cooper
2014-11-27 15:00 ` Tim Deegan
2014-11-27 15:16 ` Andrew Cooper
2014-11-27 15:28 ` Tim Deegan
2014-11-27 15:41 ` Andrew Cooper
2014-12-01 14:38 ` David Vrabel [this message]
2014-12-01 16:58 ` Andrew Cooper
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=547C7D5F.3090009@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=rshriram@cs.ubc.ca \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yanghy@cn.fujitsu.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.