All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Andrey Gruzdev via <qemu-devel@nongnu.org>
Cc: Juan Quintela <quintela@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	Peter Xu <peterx@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>,
	Den Lunev <den@openvz.org>,
	Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
Subject: Re: [PATCH v6 1/4] migration: introduce 'background-snapshot' migration capability
Date: Thu, 10 Dec 2020 13:52:36 +0100	[thread overview]
Message-ID: <878sa5su0b.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20201209100811.190316-2-andrey.gruzdev@virtuozzo.com> (Andrey Gruzdev via's message of "Wed, 9 Dec 2020 13:08:08 +0300")

Andrey Gruzdev via <qemu-devel@nongnu.org> writes:

> Add new capability to 'qapi/migration.json' schema.
> Update migrate_caps_check() to validate enabled capability set
> against introduced one. Perform checks for required kernel features
> and compatibility with guest memory backends.
>
> Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
> Reviewed-by: Peter Xu <peterx@redhat.com>
[...]
> diff --git a/qapi/migration.json b/qapi/migration.json
> index 3c75820527..6291143678 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -442,6 +442,11 @@
>  # @validate-uuid: Send the UUID of the source to allow the destination
>  #                 to ensure it is the same. (since 4.2)
>  #
> +# @background-snapshot: If enabled, the migration stream will be a snapshot
> +#                       of the VM exactly at the point when the migration
> +#                       procedure starts. The VM RAM is saved with running VM.
> +#                       (since 6.0)
> +#
>  # Since: 1.2
>  ##
>  { 'enum': 'MigrationCapability',
> @@ -449,7 +454,7 @@
>             'compress', 'events', 'postcopy-ram', 'x-colo', 'release-ram',
>             'block', 'return-path', 'pause-before-switchover', 'multifd',
>             'dirty-bitmaps', 'postcopy-blocktime', 'late-block-activate',
> -           'x-ignore-shared', 'validate-uuid' ] }
> +           'x-ignore-shared', 'validate-uuid', 'background-snapshot'] }
>  
>  ##
>  # @MigrationCapabilityStatus:

Acked-by: Markus Armbruster <armbru@redhat.com>



  reply	other threads:[~2020-12-10 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 10:08 [PATCH v6 0/4] migration: UFFD write-tracking migration/snapshots Andrey Gruzdev via
2020-12-09 10:08 ` [PATCH v6 1/4] migration: introduce 'background-snapshot' migration capability Andrey Gruzdev via
2020-12-10 12:52   ` Markus Armbruster [this message]
2020-12-09 10:08 ` [PATCH v6 2/4] migration: introduce UFFD-WP low-level interface helpers Andrey Gruzdev via
2020-12-09 10:08 ` [PATCH v6 3/4] migration: support UFFD write fault processing in ram_save_iterate() Andrey Gruzdev via
2020-12-09 10:08 ` [PATCH v6 4/4] migration: implementation of background snapshot thread Andrey Gruzdev via
2020-12-11 13:13 ` [PATCH v6 0/4] migration: UFFD write-tracking migration/snapshots Andrey Gruzdev
2020-12-11 15:09   ` Peter Xu
2020-12-15 19:52     ` Andrey Gruzdev
2020-12-15 19:53     ` Andrey Gruzdev
2020-12-16 21:02       ` Peter Xu
2020-12-17  7:50         ` Andrey Gruzdev

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=878sa5su0b.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=andrey.gruzdev@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=dgilbert@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@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.