From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Juergen Gross <JGross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Xen-devel List <xen-devel@lists.xen.org>,
Ross Lagerwall <ross.lagerwall@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: [Planning for Xen-4.6] Migration v2
Date: Wed, 26 Nov 2014 09:09:12 +0100 [thread overview]
Message-ID: <20141126080912.GA944@aepfle.de> (raw)
In-Reply-To: <5474DE5A.2060000@citrix.com>
On Tue, Nov 25, Andrew Cooper wrote:
> The purpose of this email is to plan how to progress the migrationv2
> series through to being merged. I believe I have CC'd everyone with a
> specific interest in this area, but apologies if I have missed anyone.
While you mow that lawn, did you guys think of handling downtime of the
migrated VM? I added some knobs to abort migration in a very libxc
specific way. What I would like to see is a simple user interface for
virsh/xl to control the downtime. See the thread "limit downtime during
life migration from xl/virsh":
http://lists.xenproject.org/archives/html/xen-devel/2014-03/msg00785.html
Olaf
next prev parent reply other threads:[~2014-11-26 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 19:54 [Planning for Xen-4.6] Migration v2 Andrew Cooper
2014-11-26 8:09 ` Olaf Hering [this message]
2014-11-26 13:17 ` Andrew Cooper
2014-11-26 14:53 ` Olaf Hering
2014-11-26 16:44 ` Ian Campbell
2014-11-26 17:22 ` Andrew Cooper
2014-11-26 16:50 ` Ian Campbell
2014-11-26 17:39 ` Andrew Cooper
2014-11-27 8:46 ` Ian Campbell
2014-11-27 8:33 ` Hongyang Yang
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=20141126080912.GA944@aepfle.de \
--to=olaf@aepfle.de \
--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=david.vrabel@citrix.com \
--cc=ross.lagerwall@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.