Re: [Xen-devel] question about migration

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Mon, 2016-01-04 at 15:31 +0000, Ian Jackson wrote:
> [...]

> Â The daemonic xl exits in this situation because it expects the
> Â migration machinery to tidy up the domain.
> 
> * It is not possible to resume the domain in the source after it has
> Â suspended.

Isn't supposed to be, isn't that why SCHEDOP_suspend returns a flag to
indicate if it was cancelled or not, so the guest can be resumed on the
source if "something" went wrong? (And isn't such a resume the same as what
happens after a checkpoint?)

Unless you are referring not to the general case but to some more specific
scenario/window where this is no longer possible?

> ÂÂThe domain is, in the hypervisor, in the lifecycle state
> Â SHUTDOWN.ÂÂFor this reason in general, it is a bad idea to suspend
> Â the guest until the migration is known to be likely to succeed.
> 
> Â After a late migration failure the domain should probably be treated
> Â as crashed.ÂÂThis is slightly awkward to implement because the
> Â daemonic xl would have to hang around to see what happened next and
> Â perhaps be told what to do.ÂÂOr maybe the migrating xl would have to
> Â know what the on_crash configuration was.
> 
> Â In the meantime the failure is rather less graceful: debris is
> Â simply left for the user.ÂÂThis is not ideal but tolerable I think.
> 
> Ian.
> 
> 
> From 00c4fc6495078026d68f3fdd88bfd29a8ad483d7 Mon Sep 17 00:00:00 2001
> From: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> Date: Mon, 4 Jan 2016 15:13:14 +0000
> Subject: [PATCH] libxl: Fix doc comment ref to DOMAIN_DEATH
> 
> The doc comment for libxl_evdisable_domain_death mistakenly referred
> to DOMAIN_DESTROY but the event type name is actually DOMAIN_DEATH.
> 
> Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
> CC: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
> ---
> Âtools/libxl/libxl_event.h |ÂÂÂÂ4 ++--
> Â1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/libxl/libxl_event.h b/tools/libxl/libxl_event.h
> index fad4c14..1ea789e 100644
> --- a/tools/libxl/libxl_event.h
> +++ b/tools/libxl/libxl_event.h
> @@ -179,9 +179,9 @@ typedef struct libxl__evgen_domain_death
> libxl_evgen_domain_death;
> Âint libxl_evenable_domain_death(libxl_ctx *ctx, uint32_t domid,
> ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂlibxl_ev_user, libxl_evgen_domain_death
> **evgen_out);
> Âvoid libxl_evdisable_domain_death(libxl_ctx *ctx,
> libxl_evgen_domain_death*);
> -ÂÂ/* Arranges for the generation of DOMAIN_SHUTDOWN and DOMAIN_DESTROY
> +ÂÂ/* Arranges for the generation of DOMAIN_SHUTDOWN and DOMAIN_DEATH
> ÂÂÂÂ* events.ÂÂA domain which is destroyed before it shuts down
> -ÂÂÂ* may generate only a DESTROY event.
> +ÂÂÂ* may generate only a DEATH event.
> ÂÂÂÂ*/
> Â
> Âtypedef struct libxl__evgen_disk_eject libxl_evgen_disk_eject;

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel