Il 06/11/2013 02:50, Zhanghaoyu (A) ha scritto:
> Avoid starting a new migration task while the previous one still
exist.
Can you explain how to reproduce the problem?
>>> When network disconnection between source and destination happened,
>>> the migration thread stuck at
Avoid starting a new migration task while the previous one still
>>> exist.
>>>
>>> Can you explain how to reproduce the problem?
>>>
>> When network disconnection between source and destination happened,
>> the migration thread stuck at below stack,
>> Then I cancel the migration task, the m
Il 05/11/2013 03:23, Zhanghaoyu (A) ha scritto:
>>> Avoid starting a new migration task while the previous one still
>> exist.
>>
>> Can you explain how to reproduce the problem?
>>
> When network disconnection between source and destination happened, the
> migration thread stuck at below stack,
>
> > Avoid starting a new migration task while the previous one still
> exist.
>
> Can you explain how to reproduce the problem?
>
When network disconnection between source and destination happened, the
migration thread stuck at below stack,
#0 0x7f07e96c8288 in writev () from /lib64/libc.so
On 11/04/2013 04:26 AM, Zhanghaoyu (A) wrote:
> Avoid starting a new migration task while the previous one still exist.
>
> Signed-off-by: Zeng Junliang
> ---
It's best to put comments here...
> migration.c | 34 ++
> 1 files changed, 22 insertions(+), 12 dele
Il 04/11/2013 12:26, Zhanghaoyu (A) ha scritto:
> Avoid starting a new migration task while the previous one still exist.
Can you explain how to reproduce the problem?
Also please use pbonz...@redhat.com instead. My Gmail address is an
implementation detail. :)
> Signed-off-by: Zeng Junliang
