On 03/13/2015 06:28 AM, Dr. David Alan Gilbert wrote:
>>
>> It simplifies qemu's job of reporting migration status information (qemu
>> is no longer maintaining one set of states internally and a different
>> set of states externally), and I already have the libvirt counterpart
>> patch ready to g
* Eric Blake (ebl...@redhat.com) wrote:
> On 03/13/2015 04:49 AM, Paolo Bonzini wrote:
> >
> >
> > On 09/03/2015 07:45, zhanghailiang wrote:
> >> 'cancelling' status was introduced by commit 51cf4c1a, mainly to avoid a
> >> possible start of a new migration process while the previous one still
On 03/13/2015 04:49 AM, Paolo Bonzini wrote:
>
>
> On 09/03/2015 07:45, zhanghailiang wrote:
>> 'cancelling' status was introduced by commit 51cf4c1a, mainly to avoid a
>> possible start of a new migration process while the previous one still
>> exists.
>> But we didn't expose this status to us
On 09/03/2015 07:45, zhanghailiang wrote:
> 'cancelling' status was introduced by commit 51cf4c1a, mainly to avoid a
> possible start of a new migration process while the previous one still exists.
> But we didn't expose this status to user, instead we returned the 'active'
> state.
>
> Here,
'cancelling' status was introduced by commit 51cf4c1a, mainly to avoid a
possible start of a new migration process while the previous one still exists.
But we didn't expose this status to user, instead we returned the 'active'
state.
Here, we expose it to the user (such as libvirt), 'cancelling'
