qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH RFC v4 06/13] qapi: add dirty-bitmaps migration


From: Vladimir Sementsov-Ogievskiy
Subject: Re: [Qemu-devel] [PATCH RFC v4 06/13] qapi: add dirty-bitmaps migration capability
Date: Mon, 2 Mar 2015 13:02:40 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0

On 27.02.2015 21:29, Eric Blake wrote:
On 02/27/2015 10:24 AM, Vladimir Sementsov-Ogievskiy wrote:
Reviewed-by: John Snow <address@hidden>
Signed-off-by: Vladimir Sementsov-Ogievskiy <address@hidden>
---
  include/migration/migration.h | 1 +
  migration/migration.c         | 9 +++++++++
  qapi-schema.json              | 5 ++++-
  3 files changed, 14 insertions(+), 1 deletion(-)
Reviewed-by: Eric Blake <address@hidden>


  #
+# @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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]