Re: [libvirt] [PATCH] Migration: Preserve the failed job in case migration job is terminated beyond the perform phase.

On Mon, Jan 29, 2018 at 15:56:29 +0530, Prerna wrote: > Hi Jirka, > > On Thu, Jan 25, 2018 at 8:43 PM, Jiri Denemark wrote: > > > On Thu, Jan 25, 2018 at 19:51:23 +0530, Prerna Saxena wrote: > > > In case of non-p2p migration, in case libvirt client gets disconnected > >

Re: [libvirt] [PATCH] Migration: Preserve the failed job in case migration job is terminated beyond the perform phase.

Hi Jirka, On Thu, Jan 25, 2018 at 8:43 PM, Jiri Denemark wrote: > On Thu, Jan 25, 2018 at 19:51:23 +0530, Prerna Saxena wrote: > > In case of non-p2p migration, in case libvirt client gets disconnected > from source libvirt > > after PERFORM phase is over, the daemon just

Re: [libvirt] [PATCH] Migration: Preserve the failed job in case migration job is terminated beyond the perform phase.

On Thu, Jan 25, 2018 at 19:51:23 +0530, Prerna Saxena wrote: > In case of non-p2p migration, in case libvirt client gets disconnected from > source libvirt > after PERFORM phase is over, the daemon just resets the current migration job. > However, the VM could be left paused on both source and

[libvirt] [PATCH] Migration: Preserve the failed job in case migration job is terminated beyond the perform phase.

In case of non-p2p migration, in case libvirt client gets disconnected from source libvirt after PERFORM phase is over, the daemon just resets the current migration job. However, the VM could be left paused on both source and destination in such case. In case the client reconnects and queries