From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36923) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtvCd-0006zA-1N for qemu-devel@nongnu.org; Tue, 02 Jul 2013 03:40:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UtvCb-0000BV-UQ for qemu-devel@nongnu.org; Tue, 02 Jul 2013 03:40:42 -0400 Received: from mail-wi0-x235.google.com ([2a00:1450:400c:c05::235]:59586) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtvCb-0000BH-Gd for qemu-devel@nongnu.org; Tue, 02 Jul 2013 03:40:41 -0400 Received: by mail-wi0-f181.google.com with SMTP id hq4so3874309wib.8 for ; Tue, 02 Jul 2013 00:40:40 -0700 (PDT) Date: Tue, 2 Jul 2013 09:40:38 +0200 From: Stefan Hajnoczi Message-ID: <20130702074038.GD6800@stefanha-thinkpad.redhat.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <914F6E59-6369-4060-BD75-E45B64D93719@kamp.de> 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: Peter Lieven Cc: kwolf@redhat.com, Stefan Hajnoczi , Juan Quintela , qemu-devel@nongnu.org, ronniesahlberg@gmail.com, pbonzini@redhat.com 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. CCed Juan Quintela for advice on migration. Stefan