qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 16/46] Add migration-capability boolean for post


From: Eric Blake
Subject: Re: [Qemu-devel] [PATCH 16/46] Add migration-capability boolean for postcopy-ram.
Date: Mon, 07 Jul 2014 13:41:32 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

On 07/04/2014 11:41 AM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <address@hidden>
> 
> Signed-off-by: Dr. David Alan Gilbert <address@hidden>
> ---
>  include/migration/migration.h | 1 +
>  migration.c                   | 9 +++++++++
>  qapi-schema.json              | 6 +++++-
>  3 files changed, 15 insertions(+), 1 deletion(-)
> 

> +++ b/qapi-schema.json
> @@ -491,10 +491,14 @@
>  # @auto-converge: If enabled, QEMU will automatically throttle down the guest
>  #          to speed up convergence of RAM migration. (since 1.6)
>  #
> +# @x-postcopy-ram: Start executing on the migration target before all of RAM 
> has been
> +#          migrated, pulling the remaining pages along as needed. NOTE: If 
> the
> +#          migration fails during postcopy the VM will fail.  (since 2.2)

How does this work with libvirt's current insistence that it manually
resumes the guest on the destination in order to give feedback to the
source on whether it was successful? I'm not sure if enabling this bool
is the right thing to do, or if we just need more visibility (such as
events rather than the current state of polling) for libvirt to know
that it is time to resume the destination and start the post-copy phase.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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