Re: [libvirt] [PATCH v3 4/4] migration: Expose 'cancelling' status to user

2015-03-08 Thread zhanghailiang
On 2015/3/7 0:24, Eric Blake wrote: On 03/04/2015 07:09 AM, zhanghailiang wrote: 'cancelling' status is introduced by commit 51cf4c1a, which is mainly avoid s/is introduced/was introduced/ s/which is mainly avoid/mainly to avoid a/ possible starting a new migration process while the previous

Re: [libvirt] [PATCH v3 4/4] migration: Expose 'cancelling' status to user

2015-03-06 Thread Eric Blake
On 03/04/2015 07:09 AM, zhanghailiang wrote: > 'cancelling' status is introduced by commit 51cf4c1a, which is mainly avoid s/is introduced/was introduced/ s/which is mainly avoid/mainly to avoid a/ > possible starting a new migration process while the previous one still exist. s/starting a new/s

[libvirt] [PATCH v3 4/4] migration: Expose 'cancelling' status to user

2015-03-04 Thread zhanghailiang
'cancelling' status is introduced by commit 51cf4c1a, which is mainly avoid possible starting a new migration process while the previous one still exist. But we don't expose this status to user, instead by return a 'active' state. Here, we expose it to the user (such as libvirt), 'cancelling' stat