From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60561) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSNDF-0007As-Bf for qemu-devel@nongnu.org; Mon, 02 Mar 2015 05:04:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSNDB-0006Qo-GW for qemu-devel@nongnu.org; Mon, 02 Mar 2015 05:04:33 -0500 Received: from mx2.parallels.com ([199.115.105.18]:56331) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSNDB-0006Ab-A3 for qemu-devel@nongnu.org; Mon, 02 Mar 2015 05:04:29 -0500 Message-ID: <54F43540.8040002@parallels.com> Date: Mon, 2 Mar 2015 13:02:40 +0300 From: Vladimir Sementsov-Ogievskiy MIME-Version: 1.0 References: <1425057891-29848-1-git-send-email-vsementsov@parallels.com> <1425057891-29848-7-git-send-email-vsementsov@parallels.com> <54F0B776.4090001@redhat.com> In-Reply-To: <54F0B776.4090001@redhat.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH RFC v4 06/13] qapi: add dirty-bitmaps migration capability List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake , qemu-devel@nongnu.org Cc: kwolf@redhat.com, peter.maydell@linaro.org, quintela@redhat.com, dgilbert@redhat.com, stefanha@redhat.com, pbonzini@redhat.com, amit.shah@redhat.com, den@openvz.org On 27.02.2015 21:29, Eric Blake wrote: > On 02/27/2015 10:24 AM, Vladimir Sementsov-Ogievskiy wrote: >> Reviewed-by: John Snow >> Signed-off-by: Vladimir Sementsov-Ogievskiy >> --- >> include/migration/migration.h | 1 + >> migration/migration.c | 9 +++++++++ >> qapi-schema.json | 5 ++++- >> 3 files changed, 14 insertions(+), 1 deletion(-) > Reviewed-by: Eric Blake > > >> # >> +# @dirty-bitmaps: If enabled, QEMU will migrate named dirty bitmaps. (since 2.3) > Just to make sure, this only affects the source side, and does not have > to be set on the destination (that is, the destination will > automatically handle incoming dirty bitmaps correctly without having to > tweak the knob first)? Of course, libvirt will check that the > destination advertises the feature before enabling the knob on the > source (to avoid the case of the source sending something the > destination won't understand). > Yes, live migration in the destination will call load_state iff such block is found in the migration stream. -- Best regards, Vladimir