From: Chegu Vinod <chegu_vinod@hp.com>
To: eblake@redhat.com, anthony@codemonkey.ws, quintela@redhat.com,
owasserm@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org
Cc: chegu_vinod@hp.com
Subject: [Qemu-devel] [RFC PATCH v6 0/3] Throttle-down guest to help with live migration convergence
Date: Fri, 14 Jun 2013 06:58:54 -0700 [thread overview]
Message-ID: <1371218337-51891-1-git-send-email-chegu_vinod@hp.com> (raw)
Busy enterprise workloads hosted on large sized VM's tend to dirty
memory faster than the transfer rate achieved via live guest migration.
Despite some good recent improvements (& using dedicated 10Gig NICs
between hosts) the live migration does NOT converge.
If a user chooses to force convergence of their migration via a new
migration capability "auto-converge" then this change will auto-detect
lack of convergence scenario and trigger a slow down of the workload
by explicitly disallowing the VCPUs from spending much time in the VM
context.
The migration thread tries to catchup and this eventually leads
to convergence in some "deterministic" amount of time. Yes it does
impact the performance of all the VCPUs but in our observation that
lasts only for a short duration of time. i.e. end up entering
stage 3 (downtime phase) soon after that. No external monitoring/triggers
are required.
Thanks to Juan and Paolo for their useful suggestions.
---
Changes from v5:
- incorporated feedback from Paolo & Igor.
- rebased to latest qemu.git
Changes from v4:
- incorporated feedback from Paolo.
- split into 3 patches.
Changes from v3:
- incorporated feedback from Paolo and Eric
- rebased to latest qemu.git
Changes from v2:
- incorporated feedback from Orit, Juan and Eric
- stop the throttling thread at the start of stage 3
- rebased to latest qemu.git
Changes from v1:
- rebased to latest qemu.git
- added auto-converge capability(default off) - suggested by Anthony Liguori &
Eric Blake.
Signed-off-by: Chegu Vinod <chegu_vinod@hp.com>
---
Chegu Vinod (3):
Introduce async_run_on_cpu()
Add 'auto-converge' migration capability
Force auto-convegence of live migration
arch_init.c | 85 +++++++++++++++++++++++++++++++++++++++++
cpus.c | 29 ++++++++++++++
include/migration/migration.h | 2 +
include/qemu-common.h | 1 +
include/qom/cpu.h | 10 +++++
migration.c | 9 ++++
qapi-schema.json | 5 ++-
7 files changed, 140 insertions(+), 1 deletions(-)
next reply other threads:[~2013-06-14 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 13:58 Chegu Vinod [this message]
2013-06-14 13:58 ` [Qemu-devel] [RFC PATCH v6 1/3] Introduce async_run_on_cpu() Chegu Vinod
2013-06-14 13:58 ` [Qemu-devel] [RFC PATCH v6 2/3] Add 'auto-converge' migration capability Chegu Vinod
2013-06-14 13:58 ` [Qemu-devel] [RFC PATCH v6 3/3] Force auto-convegence of live migration Chegu Vinod
2013-06-20 12:54 ` Paolo Bonzini
2013-06-24 2:08 ` Chegu Vinod
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=1371218337-51891-1-git-send-email-chegu_vinod@hp.com \
--to=chegu_vinod@hp.com \
--cc=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).