From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>,
david@redhat.com, zhang.zhanghailiang@huawei.com
Cc: quintela@redhat.com, qemu-devel@nongnu.org, peterx@redhat.com,
armbru@redhat.com, den@openvz.org, pbonzini@redhat.com
Subject: Re: [PATCH v0 0/4] background snapshot
Date: Mon, 27 Jul 2020 17:59:35 +0100 [thread overview]
Message-ID: <20200727165935.GS3040@work-vm> (raw)
In-Reply-To: <20200722081133.29926-1-dplotnikov@virtuozzo.com>
* Denis Plotnikov (dplotnikov@virtuozzo.com) wrote:
> Currently where is no way to make a vm snapshot without pausing a vm
> for the whole time until the snapshot is done. So, the problem is
> the vm downtime on snapshoting. The downtime value depends on the vmstate
> size, the major part of which is RAM and the disk performance which is
> used for the snapshot saving.
>
> The series propose a way to reduce the vm snapshot downtime. This is done
> by saving RAM, the major part of vmstate, in the background when the vm
> is running.
>
> The background snapshot uses linux UFFD write-protected mode for memory
> page access intercepting. UFFD write-protected mode was added to the linux v5.7.
> If UFFD write-protected mode isn't available the background snapshot rejects to
> run.
Hi Denis,
I see Peter has responded to most of your patches, but just anted to
say thank you; but also to cc in a couple of other people;
David Hildenbrand (who is interested in unusual memory stuff) and
zhanghailiang who works on COLO which also does snapshotting and had
long wanted to use WP.
2/4 was a bit big for my liking; please try and do it in smaller
chunks!
Dave
> How to use:
> 1. enable background snapshot capability
> virsh qemu-monitor-command vm --hmp migrate_set_capability background-snapshot on
>
> 2. stop the vm
> virsh qemu-monitor-command vm --hmp stop
>
> 3. Start the external migration to a file
> virsh qemu-monitor-command cent78-bs --hmp migrate exec:'cat > ./vm_state'
>
> 4. Wait for the migration finish and check that the migration has completed state.
>
> Denis Plotnikov (4):
> bitops: add some atomic versions of bitmap operations
> migration: add background snapshot capability
> migration: add background snapshot
> background snapshot: add trace events for page fault processing
>
> qapi/migration.json | 7 +-
> include/exec/ramblock.h | 8 +
> include/exec/ramlist.h | 2 +
> include/qemu/bitops.h | 25 ++
> migration/migration.h | 1 +
> migration/ram.h | 19 +-
> migration/savevm.h | 3 +
> migration/migration.c | 142 +++++++++-
> migration/ram.c | 582 ++++++++++++++++++++++++++++++++++++++--
> migration/savevm.c | 1 -
> migration/trace-events | 2 +
> 11 files changed, 771 insertions(+), 21 deletions(-)
>
> --
> 2.17.0
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-07-27 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 8:11 [PATCH v0 0/4] background snapshot Denis Plotnikov
2020-07-22 8:11 ` [PATCH v0 1/4] bitops: add some atomic versions of bitmap operations Denis Plotnikov
2020-07-22 8:11 ` [PATCH v0 2/4] migration: add background snapshot capability Denis Plotnikov
2020-07-23 22:21 ` Peter Xu
2020-07-22 8:11 ` [PATCH v0 3/4] migration: add background snapshot Denis Plotnikov
2020-07-23 22:15 ` Peter Xu
2020-07-29 12:27 ` Denis Plotnikov
2020-07-24 0:08 ` Peter Xu
2020-07-29 12:54 ` Denis Plotnikov
2020-07-29 16:58 ` Peter Xu
2020-07-27 16:48 ` Dr. David Alan Gilbert
2020-07-28 9:34 ` Denis Plotnikov
2020-07-29 13:27 ` Dr. David Alan Gilbert
2020-07-29 13:57 ` Denis Plotnikov
2020-07-22 8:11 ` [PATCH v0 4/4] background snapshot: add trace events for page fault processing Denis Plotnikov
2020-07-22 14:50 ` [PATCH v0 0/4] background snapshot Peter Xu
2020-07-22 15:42 ` Denis Plotnikov
2020-07-22 15:47 ` Denis Plotnikov
2020-07-22 16:30 ` Peter Xu
2020-07-23 8:03 ` Denis Plotnikov
2020-07-23 17:39 ` Peter Xu
2020-07-24 8:06 ` Denis Plotnikov
2020-07-24 16:31 ` Peter Xu
2020-07-27 16:59 ` Dr. David Alan Gilbert [this message]
2020-08-04 13:11 ` Zhanghailiang
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=20200727165935.GS3040@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=david@redhat.com \
--cc=den@openvz.org \
--cc=dplotnikov@virtuozzo.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).