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 below stack,
Then I
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,
#0
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 migration state in
Avoid starting a new migration task while the previous one still exist.
Signed-off-by: Zeng Junliang zengjunli...@huawei.com
---
migration.c | 34 ++
1 files changed, 22 insertions(+), 12 deletions(-)
diff --git a/migration.c b/migration.c
index
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
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 zengjunli...@huawei.com
---
It's best to put comments here...
migration.c | 34 ++
1 files changed, 22
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.6
#1
