On 05/12/2017 06:31 AM, Alexey Perevalov wrote:
> Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
> ---
> docs/migration.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/docs/migration.txt b/docs/migration.txt
> index 1b940a8..d0f5a6d 100644
> --- a/docs/migration.txt
> +++ b/docs/migration.txt
> @@ -402,6 +402,16 @@ will now cause the transition from precopy to postcopy.
> It can be issued immediately after migration is started or any
> time later on. Issuing it after the end of a migration is harmless.
>
> +Blocktime it's a postcopy live migration metric, intend to show
s/it's/is/
s/intend/intended/
> +when source vCPU was in state interruptable sleep due to pagefault.
s/when/how long the/
> +This value is calculated on destination side.
> +To enable postcopy blocktime calculation, enter following command on destination
> +monitor:
> +
> +migrate_set_capability postcopy-blocktime on
> +
> +Postcopy blocktime could be retrieved by query-migrate qmp command.
s/could/can/
> +
> Note: During the postcopy phase, the bandwidth limits set using
> migrate_set_speed is ignored (to avoid delaying requested pages that
> the destination is waiting for).
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org