From: Bohdan Trach <bohdan.trach@mailbox.tu-dresden.de>
To: qemu-devel@nongnu.org
Cc: Bohdan Trach <bohdan.trach@mailbox.tu-dresden.de>,
amit.shah@redhat.com, thomas.knauth@googlemail.com,
quintela@redhat.com
Subject: [Qemu-devel] [RFC V2, PATCH 0/2] Checkpoint-assisted migration proposal
Date: Tue, 24 Nov 2015 17:42:27 +0100 [thread overview]
Message-ID: <cover.1448378993.git.bohdan.trach@mailbox.tu-dresden.de> (raw)
Changes from V1:
- Use ELF dumps produced by the dump-guest-memory command;
- Use checkpoints for all memory blocks;
- Use trace_ instead of DPRINTF;
- removed RAM_SAVE_FLAG_PAGE_HASH flag;
- General code cleanup and update to latest QEMU codebase.
This patchset contains a checkpoint-assisted migration feature as
proposed earlier on this list [1]. It allows reusing existing memory
snapshots of guests to speed up migration of VMs between physical
hosts.
[1] https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg01555.html
Bohdan Trach (2):
migration: implement checkpoint loading
migration: use checkpoint during migration
include/migration/migration.h | 4 +
migration/ram.c | 288 ++++++++++++++++++++++++++++++++++++++++--
qemu-options.hx | 9 ++
trace-events | 8 ++
vl.c | 9 ++
5 files changed, 309 insertions(+), 9 deletions(-)
--
2.4.10
next reply other threads:[~2015-11-24 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 16:42 Bohdan Trach [this message]
2015-11-24 16:42 ` [Qemu-devel] [PATCH RFC 1/2] migration: implement checkpoint loading Bohdan Trach
2015-11-24 16:42 ` [Qemu-devel] [PATCH RFC 2/2] migration: use checkpoint during migration Bohdan Trach
2015-11-24 17:51 ` [Qemu-devel] [RFC V2, PATCH 0/2] Checkpoint-assisted migration proposal Eric Blake
2015-11-25 10:24 ` Bohdan Trach
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=cover.1448378993.git.bohdan.trach@mailbox.tu-dresden.de \
--to=bohdan.trach@mailbox.tu-dresden.de \
--cc=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thomas.knauth@googlemail.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).