[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 0/7] UFFD write-tracking migration/snapshots

From: Andrey Gruzdev
Subject: Re: [PATCH v2 0/7] UFFD write-tracking migration/snapshots
Date: Thu, 19 Nov 2020 10:26:55 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

On 18.11.2020 17:54, Eric Blake wrote:
On 11/18/20 7:20 AM, Andrey Gruzdev wrote:
Currently the only way to make (external) live VM snapshot is using existing
dirty page logging migration mechanism. The main problem is that it tends to
produce a lot of page duplicates while running VM goes on updating already
saved pages. That leads to the fact that vmstate image size is commonly several
times bigger then non-zero part of virtual machine's RSS. Time required to
converge RAM migration and the size of snapshot image severely depend on the
guest memory write rate, sometimes resulting in unacceptably long snapshot
creation time and huge image size.

This series propose a way to solve the aforementioned problems. This is done
by using different RAM migration mechanism based on UFFD write protection
management introduced in v5.7 kernel. The migration strategy is to 'freeze'
guest RAM content using write-protection and iteratively release protection
for memory ranges that have already been saved to the migration stream.
At the same time we read in pending UFFD write fault events and save those
pages out-of-order with higher priority.

How to use:
1. Enable write-tracking migration capability
    virsh qemu-monitor-command <domain> --hmp migrate_set_capability.
track-writes-ram on

2. Start the external migration to a file
    virsh qemu-monitor-command <domain> --hmp migrate exec:'cat > ./vm_state'

3. Wait for the migration finish and check that the migration has completed.

Andrey Gruzdev (7):
   Introduce 'track-writes-ram' migration capability.
   Introduced UFFD-WP low-level interface helpers. Implemented support
     for the whole RAM block memory protection/un-protection. Higher
     level ram_write_tracking_start() and ram_write_tracking_stop() to
     start/stop tracking memory writes on the whole VM memory.

Subject line is too long on that patch. You probably forgot a newline.
Also, it is more common to not include a trailing '.' in the subject line.

Sorry, I'm a bit new to mailing list process, indeed I missed newline to separate subject.

   Support UFFD write fault processing in ram_save_iterate().
   Implementation of write-tracking migration thread.
   Implementation of vm_start() BH.
   The rest of write tracking migration code.
   Introduced simple linear scan rate limiting mechanism for write
     tracking migration.

How does v2 differ from v1?  It makes life easier for reviewers to know
what to look for in the respin that was fixed based on the problems in
the earlier version.

The only difference v0->v2 is that the latter would pass checkpatch test, nothing else. I've accidently disabled checkpatch commit hook
after found it's false positive on do {} while (0); - for the semicolon.

Andrey Gruzdev, Principal Engineer
Virtuozzo GmbH  +7-903-247-6397

reply via email to

[Prev in Thread] Current Thread [Next in Thread]