On Fri, Jan 22, 2016 at 15:07:04 +, Daniel P. Berrange wrote:
> On Thu, Jan 21, 2016 at 11:20:46AM +0100, Jiri Denemark wrote:
> > VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY and VIR_DOMAIN_PAUSED_POSTCOPY are
> > used on the source host once migration enters post-copy mode (which
> > means the domain
On Fri, Jan 22, 2016 at 15:23:43 +, Daniel P. Berrange wrote:
> On Fri, Jan 22, 2016 at 04:17:42PM +0100, Jiri Denemark wrote:
> > On Fri, Jan 22, 2016 at 15:07:04 +, Daniel P. Berrange wrote:
> > > On Thu, Jan 21, 2016 at 11:20:46AM +0100, Jiri Denemark wrote:
> > > >
On Thu, Jan 21, 2016 at 11:20:46AM +0100, Jiri Denemark wrote:
> VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY and VIR_DOMAIN_PAUSED_POSTCOPY are
> used on the source host once migration enters post-copy mode (which
> means the domain gets paused on the source. After the destination host
> takes over the
On Fri, Jan 22, 2016 at 04:17:42PM +0100, Jiri Denemark wrote:
> On Fri, Jan 22, 2016 at 15:07:04 +, Daniel P. Berrange wrote:
> > On Thu, Jan 21, 2016 at 11:20:46AM +0100, Jiri Denemark wrote:
> > > VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY and VIR_DOMAIN_PAUSED_POSTCOPY are
> > > used on the
VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY and VIR_DOMAIN_PAUSED_POSTCOPY are
used on the source host once migration enters post-copy mode (which
means the domain gets paused on the source. After the destination host
takes over the execution of the domain, its virtual CPUs are resumed and
the domain