From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49292) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dAdaX-00084g-7K for qemu-devel@nongnu.org; Tue, 16 May 2017 10:36:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dAdaT-0005jw-AN for qemu-devel@nongnu.org; Tue, 16 May 2017 10:36:37 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38704) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dAdaT-0005jX-4f for qemu-devel@nongnu.org; Tue, 16 May 2017 10:36:33 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F213B804F6 for ; Tue, 16 May 2017 14:36:21 +0000 (UTC) From: Juan Quintela In-Reply-To: <87o9usg9v7.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Tue, 16 May 2017 16:22:04 +0200") References: <20170516111123.17692-1-quintela@redhat.com> <20170516111123.17692-4-quintela@redhat.com> <87o9usg9v7.fsf@dusky.pond.sub.org> Reply-To: quintela@redhat.com Date: Tue, 16 May 2017 16:36:10 +0200 Message-ID: <87inl0dg2t.fsf@secure.mitica> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH 3/5] migration: Remove use of old MigrationParams List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: qemu-devel@nongnu.org, lvivier@redhat.com, dgilbert@redhat.com, peterx@redhat.com Markus Armbruster wrote: > Juan Quintela 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 >> 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. Later, Juan.