* Peter Xu (pet...@redhat.com) wrote:
> On Thu, Oct 19, 2017 at 12:21:23PM +0100, Dr. David Alan Gilbert wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > On Wed, Oct 18, 2017 at 06:40:06PM +0100, Dr. David Alan Gilbert (git)
> > > wrote:
> > >
> > > [...]
> > >
> > > > The precopy flow is:
On Thu, Oct 19, 2017 at 12:21:23PM +0100, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > On Wed, Oct 18, 2017 at 06:40:06PM +0100, Dr. David Alan Gilbert (git)
> > wrote:
> >
> > [...]
> >
> > > The precopy flow is:
> > > active->pre-switchover->device->completed
> > >
* Jiri Denemark (jdene...@redhat.com) wrote:
> The libvirt changes which will make use of this new migration capability
> can be found in migration-pause branch of my gitlab repository:
>
> git fetch https://gitlab.com/jirkade/libvirt.git migration-pause
>
> It's not properly split into patch
The libvirt changes which will make use of this new migration capability
can be found in migration-pause branch of my gitlab repository:
git fetch https://gitlab.com/jirkade/libvirt.git migration-pause
It's not properly split into patches, it has no commit message etc.,
but the functionality
* Peter Xu (pet...@redhat.com) wrote:
> On Wed, Oct 18, 2017 at 06:40:06PM +0100, Dr. David Alan Gilbert (git) wrote:
>
> [...]
>
> > The precopy flow is:
> > active->pre-switchover->device->completed
> >
> > The postcopy flow is:
> > active->pre-switchover->postcopy-active->completed
>
> The n
On Wed, Oct 18, 2017 at 06:40:06PM +0100, Dr. David Alan Gilbert (git) wrote:
[...]
> The precopy flow is:
> active->pre-switchover->device->completed
>
> The postcopy flow is:
> active->pre-switchover->postcopy-active->completed
The naming is still slightly confusing to me:
(1) we have a capa