From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49999) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtyBC-0001SE-Jv for qemu-devel@nongnu.org; Tue, 02 Jul 2013 06:51:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UtyBB-0002nN-OD for qemu-devel@nongnu.org; Tue, 02 Jul 2013 06:51:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39026) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtyBB-0002n6-8s for qemu-devel@nongnu.org; Tue, 02 Jul 2013 06:51:25 -0400 Message-ID: <51D2B0A2.1080606@redhat.com> Date: Tue, 02 Jul 2013 12:51:14 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1372338695-411-1-git-send-email-pl@kamp.de> <1372338695-411-9-git-send-email-pl@kamp.de> <20130701141305.GE20182@stefanha-thinkpad.redhat.com> <914F6E59-6369-4060-BD75-E45B64D93719@kamp.de> <20130702074038.GD6800@stefanha-thinkpad.redhat.com> In-Reply-To: <20130702074038.GD6800@stefanha-thinkpad.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCHv2 08/11] block-migration: efficiently encode zero blocks List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: kwolf@redhat.com, Stefan Hajnoczi , Juan Quintela , Peter Lieven , qemu-devel@nongnu.org, ronniesahlberg@gmail.com Il 02/07/2013 09:40, Stefan Hajnoczi ha scritto: > On Mon, Jul 01, 2013 at 05:55:15PM +0200, Peter Lieven wrote: >> >> Am 01.07.2013 um 16:13 schrieb Stefan Hajnoczi : >> >>> On Thu, Jun 27, 2013 at 03:11:32PM +0200, Peter Lieven wrote: >>> >>> This patch breaks cross-version blog migration. We need to control >>> whether or not to use the new BLK_MIG_FLAG_ZERO_BLOCK flag. >> >> you are right the upgrade way works, but downgrade not. what is the >> proposed way to fix this? > > The safest way is to add a block migration flag that toggles the zero > block. By default it would be off. > > Maybe you would also add a MigrationCapability in qapi-schema.json to > indicated that zero blocks are supported in block migration. That would > allow management tools to ask QEMU on both sides if they support zero > blocks. > > Use migrate-set-capabilities to enable the zero block feature. Yes, a capability makes sense. Paolo