From: Markus Armbruster <armbru@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: lvivier@redhat.com, qemu-devel@nongnu.org, peterx@redhat.com,
dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/5] migration: Remove use of old MigrationParams
Date: Tue, 16 May 2017 17:35:40 +0200 [thread overview]
Message-ID: <87shk4byr7.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <87inl0dg2t.fsf@secure.mitica> (Juan Quintela's message of "Tue, 16 May 2017 16:36:10 +0200")
Juan Quintela <quintela@redhat.com> writes:
> Markus Armbruster <armbru@redhat.com> wrote:
>> Juan Quintela <quintela@redhat.com> writes:
>>
>>> We have change in the previous patch to use migration capabilities for
>>> it. Notice that we continue using the old command line flags from
>>> migrate command from the time being. Remove the set_params method as
>>> now it is empty.
>>>
>>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>
>>> diff --git a/migration/savevm.c b/migration/savevm.c
>>> index b4f736f..5fc10ab 100644
>>> --- a/migration/savevm.c
>>> +++ b/migration/savevm.c
>>> @@ -1233,8 +1233,6 @@ static int qemu_savevm_state(QEMUFile *f, Error **errp)
>>> {
>>> int ret;
>>> MigrationParams params = {
>>> - .blk = 0,
>>> - .shared = 0
>>> };
>>> MigrationState *ms = migrate_init(¶ms);
>>> MigrationStatus status;
>>> @@ -1245,6 +1243,12 @@ static int qemu_savevm_state(QEMUFile *f, Error **errp)
>>> goto done;
>>> }
>>>
>>> + if (migrate_use_block()) {
>>> + error_setg(errp, "Block migration and snapshots are incompatible");
>>> + ret = -EINVAL;
>>> + goto done;
>>> + }
>>> +
>>> qemu_mutex_unlock_iothread();
>>> qemu_savevm_state_header(f);
>>> qemu_savevm_state_begin(f, ¶ms);
>>
>> New error that isn't mentioned in the commit message. Does it belong
>> here?
>
> It is the equivalent of the previous chunk.
>
> If you do a savevm, you can't do a:
>
> savevm -b/-i foo
>
> but now you can do:
>
> migrate_set_capability block on
> savevm foo
>
> And we can't use block migration. If you preffer, I can disable the
> feature unconditionally, but I am not sure that it is much better.
I see.
Add your explanation to the commit message, and I'm happy.
next prev parent reply other threads:[~2017-05-16 15:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 11:11 [Qemu-devel] [PATCH v4 0/5] Remove old MigrationParams Juan Quintela
2017-05-16 11:11 ` [Qemu-devel] [PATCH 1/5] hmp: Use visitor api for hmp_migrate_set_parameter() Juan Quintela
2017-05-16 12:29 ` Markus Armbruster
2017-05-16 11:11 ` [Qemu-devel] [PATCH 2/5] migration: Create block capability Juan Quintela
2017-05-16 14:20 ` Markus Armbruster
2017-05-16 14:34 ` Juan Quintela
2017-05-16 16:00 ` Markus Armbruster
2017-05-16 16:08 ` Eric Blake
2017-05-16 16:42 ` Markus Armbruster
2017-05-16 16:48 ` Eric Blake
2017-05-16 17:07 ` Markus Armbruster
2017-05-16 17:37 ` Juan Quintela
2017-05-16 11:11 ` [Qemu-devel] [PATCH 3/5] migration: Remove use of old MigrationParams Juan Quintela
2017-05-16 14:22 ` Markus Armbruster
2017-05-16 14:36 ` Juan Quintela
2017-05-16 15:35 ` Markus Armbruster [this message]
2017-05-16 11:11 ` [Qemu-devel] [PATCH 4/5] migration: Remove " Juan Quintela
2017-05-16 11:11 ` [Qemu-devel] [PATCH 5/5] block migration: Allow compile time disable Juan Quintela
2017-05-17 15:38 [Qemu-devel] [PATCH v5 0/5] Remove old MigrationParams Juan Quintela
2017-05-17 15:38 ` [Qemu-devel] [PATCH 3/5] migration: Remove use of " Juan Quintela
2017-05-17 15:54 ` Eric Blake
2017-05-17 16:18 ` Juan Quintela
2017-05-24 12:28 ` Markus Armbruster
2017-05-24 12:44 ` Markus Armbruster
2017-05-18 11:18 [Qemu-devel] [PATCH 0/5] Remove " Juan Quintela
2017-05-18 11:18 ` [Qemu-devel] [PATCH 3/5] migration: Remove use of " Juan Quintela
2017-05-19 10:54 ` Markus Armbruster
2017-05-24 12:48 ` Markus Armbruster
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=87shk4byr7.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@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.