From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57291) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAfte-0001oj-Sm for qemu-devel@nongnu.org; Mon, 12 Jan 2015 09:23:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YAftb-0008A9-Ci for qemu-devel@nongnu.org; Mon, 12 Jan 2015 09:23:10 -0500 Received: from mx2.parallels.com ([199.115.105.18]:47836) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAftb-0007pw-6g for qemu-devel@nongnu.org; Mon, 12 Jan 2015 09:23:07 -0500 Message-ID: <54B3D84A.8000207@parallels.com> Date: Mon, 12 Jan 2015 17:20:58 +0300 From: Vladimir Sementsov-Ogievskiy MIME-Version: 1.0 References: <1418307457-25996-1-git-send-email-vsementsov@parallels.com> <1418307457-25996-10-git-send-email-vsementsov@parallels.com> <54AF0662.7050303@redhat.com> In-Reply-To: <54AF0662.7050303@redhat.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 9/9] block-migration: add named dirty bitmaps migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , qemu-devel@nongnu.org Cc: kwolf@redhat.com, den@openvz.org, jsnow@redhat.com, stefanha@redhat.com Best regards, Vladimir On 09.01.2015 01:36, Paolo Bonzini wrote: > The bitmaps are transmitted many times in their entirety, but only the > last copy actually means something. The others are lost. This means > you should use the non-live interface (register_savevm). This will > simplify the code a lot. But what if the dirty bitmap is really big? For example, for 5 Pb drive the bitmap with granularity 65536 will be of 2 Gb size. So, shouldn't it be migrated iteratively for live migration?