From: Juan Quintela <quintela@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "Fam Zheng" <fam@euphon.net>,
"Eric Blake" <eblake@redhat.com>,
libvir-list@redhat.com, "Leonardo Bras" <leobras@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>, "Peter Xu" <peterx@redhat.com>,
qemu-block@nongnu.org, "Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v3 1/4] migration: migrate 'inc' command option is deprecated.
Date: Thu, 12 Oct 2023 12:50:00 +0200 [thread overview]
Message-ID: <87il7c6ron.fsf@secure.mitica> (raw)
In-Reply-To: <87zg0oyxpz.fsf@pond.sub.org> (Markus Armbruster's message of "Thu, 12 Oct 2023 11:52:08 +0200")
Markus Armbruster <armbru@redhat.com> wrote:
> Juan Quintela <quintela@redhat.com> writes:
>
>> Set the 'block_incremental' migration parameter to 'true' instead.
>>
>> # @blk: do block migration (full disk copy)
>> #
>> -# @inc: incremental disk copy migration
>> +# @inc: incremental disk copy migration. This option is deprecated.
>> +# Set the 'block-incremetantal' migration parameter to 'true'
>> +# instead.
>
> 'block-incremental'
Done, thanks.
>> #
>> # @detach: this argument exists only for compatibility reasons and is
>> # ignored by QEMU
>> #
>> # @resume: resume one paused migration, default "off". (since 3.0)
>> #
>> +# Features:
>> +#
>> +# @deprecated: option @inc should be enabled by setting the
>> +# 'block-incremental' migration parameter to 'true'.
>> +#
>
> You add deprecation notices, one to the member documentation, and one to
> the "Features:" section. You should add just one, to the "Features:"
> section. Suggest:
>
> # @deprecated: Member @inc is deprecated. Use migration parameter
> # @block-incremental instead.
Done.
>> # Returns: nothing on success
>> #
>> # Since: 0.14
>> @@ -1514,7 +1521,8 @@
>> # <- { "return": {} }
>> ##
>> { 'command': 'migrate',
>> - 'data': {'uri': 'str', '*blk': 'bool', '*inc': 'bool',
>> + 'data': {'uri': 'str', '*blk': 'bool',
>> + '*inc': { 'type': 'bool', 'features': ['deprecated'] },
>
> For better or worse, we format like [ 'deprecated' ].
Done.
>> '*detach': 'bool', '*resume': 'bool' } }
>>
>> ##
>> diff --git a/migration/migration.c b/migration/migration.c
>> index 1c6c81ad49..c7e4c37b8a 100644
>> --- a/migration/migration.c
>> +++ b/migration/migration.c
>> @@ -1601,6 +1601,12 @@ static bool migrate_prepare(MigrationState *s, bool blk, bool blk_inc,
>> {
>> Error *local_err = NULL;
>>
>> + if (blk_inc) {
>> + warn_report("-inc migrate option is deprecated, set the "
>> + "'block-incremental' migration parameter to 'true'"
>> + " instead.");
>
> There is no "-inc migrate option". You're refering to QMP command
> migrate's parameter @inc / HMP command migrate's flag -i.
Changed to:
s|-inc|@inc/-i|
>> + }
>> +
>> if (resume) {
>> if (s->state != MIGRATION_STATUS_POSTCOPY_PAUSED) {
>> error_setg(errp, "Cannot resume if there is no "
>
> As far as I can see, HMP command migrate still uses the deprecated
> interface:
>
> qmp_migrate(uri, !!blk, blk, !!inc, inc,
> false, false, true, resume, &err);
>
> Its use should be replaced before we deprecate it.
We need to drop it.
Blockjobs are much more flexible. We want to get rid of the whole
concept of block migration inside the migration protocol/machinery.
Block migration requires that one:
- migrate all devices, i.e. no way to select some shared some local.
- I think that incremental bit requires that you use qcow2 images, but I
haven't even double checked them.
I just want to drop it in the near future, if 9.0 is too soon, for
10.0.
Later, Juan.
next prev parent reply other threads:[~2023-10-12 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 20:47 [PATCH v3 0/4] Migration deprecated parts Juan Quintela
2023-10-11 20:47 ` [PATCH v3 1/4] migration: migrate 'inc' command option is deprecated Juan Quintela
2023-10-12 9:52 ` Markus Armbruster
2023-10-12 10:50 ` Juan Quintela [this message]
2023-10-11 20:47 ` [PATCH v3 2/4] migration: migrate 'blk' " Juan Quintela
2023-10-11 20:47 ` [PATCH v3 3/4] migration: Deprecate block migration Juan Quintela
2023-10-12 10:01 ` Markus Armbruster
2023-10-12 11:06 ` Kevin Wolf
2023-10-12 12:04 ` Juan Quintela
2023-10-11 20:47 ` [PATCH v3 4/4] migration: Deprecate old compression method Juan Quintela
2023-10-12 10:06 ` Markus Armbruster
2023-10-12 12:14 ` Juan Quintela
2023-10-11 21:02 ` [PATCH v3 0/4] Migration deprecated parts Stefan Hajnoczi
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=87il7c6ron.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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 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).