From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: dgilbert@redhat.com, quintela@redhat.com, pbonzini@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v1 00/17] Background snapshots
Date: Wed, 18 Jul 2018 18:41:43 +0300 [thread overview]
Message-ID: <20180718154200.26777-1-dplotnikov@virtuozzo.com> (raw)
The workflow to make a snapshot is the following:
1. Pause the vm
2. Make a snapshot of block devices using the scheme of your choice
3. Turn on background-snapshot migration capability
4. Start the migration using the destination (migration stream) of your choice.
The migration will resume the vm execution by itself
when it has the devices' states saved and is ready to start ram writing
to the migration stream.
5. Listen to the migration finish event
The bakground snapshot works with support of KVM patch:
"x86: mmu: report failed memory access to the userspace"
(not applied to the mainstream, it's in the kvm mailing list)
--
Change log:
v0 => v1:
============
the patch series has been split in smaller chunks
Denis Plotnikov (17):
migration: add background snapshot capability
bitops: add some atomic versions of bitmap operations
threads: add infrastructure to process sigsegv
background snapshot: make a dedicated type for ram block list
ram: extend the data structures for background snapshotting
background snapshot: add helpers to manage a copy of ram block list
background snapshot: introduce page buffer
migration: add helpers to change VM memory protection rights
background snapshot: extend RAM request for holding a page copy
pointer
background snapshots: adapt the page queueing code for using page
copies
background snapshot: add a memory page copying function
ram: add background snapshot support in ram page saving part of
migration
background snapshot: add write-protected page access handler function
kvm: add failed memeory access exit reason
kvm: add vCPU failed memeory access processing
migration: move the device state saving logic to a separate function
background snapshot: enable background snapshot
include/exec/ram_addr.h | 7 +
include/exec/ramlist.h | 4 +-
include/qemu/bitops.h | 25 +++
include/qemu/thread.h | 5 +
linux-headers/linux/kvm.h | 5 +
migration/migration.c | 140 +++++++++++++-
migration/migration.h | 1 +
migration/ram.c | 374 ++++++++++++++++++++++++++++++++++++--
migration/ram.h | 17 +-
migration/savevm.c | 91 +++++-----
migration/savevm.h | 2 +
qapi/migration.json | 6 +-
target/i386/kvm.c | 17 ++
util/qemu-thread-posix.c | 52 ++++++
14 files changed, 684 insertions(+), 62 deletions(-)
--
2.17.0
next reply other threads:[~2018-07-18 15:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 15:41 Denis Plotnikov [this message]
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 01/17] migration: add background snapshot capability Denis Plotnikov
2018-07-20 5:14 ` Peter Xu
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 02/17] bitops: add some atomic versions of bitmap operations Denis Plotnikov
2018-07-20 5:09 ` Peter Xu
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 03/17] threads: add infrastructure to process sigsegv Denis Plotnikov
2018-07-20 4:58 ` Peter Xu
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 04/17] background snapshot: make a dedicated type for ram block list Denis Plotnikov
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 05/17] ram: extend the data structures for background snapshotting Denis Plotnikov
2018-07-20 7:59 ` Peter Xu
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 06/17] background snapshot: add helpers to manage a copy of ram block list Denis Plotnikov
2018-07-20 7:57 ` Peter Xu
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 07/17] background snapshot: introduce page buffer Denis Plotnikov
2018-07-20 9:22 ` Peter Xu
2018-07-20 10:34 ` Paolo Bonzini
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 08/17] migration: add helpers to change VM memory protection rights Denis Plotnikov
2018-07-20 11:28 ` Dr. David Alan Gilbert
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 09/17] background snapshot: extend RAM request for holding a page copy pointer Denis Plotnikov
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 10/17] background snapshots: adapt the page queueing code for using page copies Denis Plotnikov
2018-07-20 8:39 ` Peter Xu
2018-07-20 11:46 ` Peter Xu
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 11/17] background snapshot: add a memory page copying function Denis Plotnikov
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 12/17] ram: add background snapshot support in ram page saving part of migration Denis Plotnikov
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 13/17] background snapshot: add write-protected page access handler function Denis Plotnikov
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 14/17] kvm: add failed memeory access exit reason Denis Plotnikov
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 15/17] kvm: add vCPU failed memeory access processing Denis Plotnikov
2018-07-20 9:44 ` Peter Xu
2018-07-18 15:41 ` [Qemu-devel] [PATCH v1 16/17] migration: move the device state saving logic to a separate function Denis Plotnikov
2018-07-18 15:42 ` [Qemu-devel] [PATCH v1 17/17] background snapshot: enable background snapshot Denis Plotnikov
2018-07-20 9:27 ` [Qemu-devel] [PATCH v1 00/17] Background snapshots Peter Xu
2018-09-04 13:00 ` Denis Plotnikov
2018-09-05 3:32 ` Peter Xu
2018-09-05 9:18 ` Denis Plotnikov
2018-09-05 9:30 ` Peter Xu
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=20180718154200.26777-1-dplotnikov@virtuozzo.com \
--to=dplotnikov@virtuozzo.com \
--cc=dgilbert@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 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.