[Qemu-discuss] 答复: Latest Qemu-COLO Problems

[wenzt]

Thanks for help !

 

I don’t know why we keep switching SVM between Run and Stop ?

Why we don’t keep SVM inmigration status ?

 

Thanks, 

Zhengtao

 

发件人: Zhang, Chen <address@hidden> 
发送时间: 2019年2月26日 18:41
收件人: wenzt <address@hidden>
抄送: 'qemu-discuss' <address@hidden>
主题: RE: Latest Qemu-COLO Problems

 

By the way, please read the COLO wiki use this command to trigger failover
in secondary node:

 

{ 'execute': 'nbd-server-stop' }

{ "execute": "x-colo-lost-heartbeat" }

 

 

Thanks

Zhang Chen

 

From: Zhang, Chen 
Sent: Tuesday, February 26, 2019 2:46 PM
To: 'wenzt' <address@hidden <mailto:address@hidden> >
Cc: 'qemu-discuss' <address@hidden <mailto:address@hidden>
>
Subject: RE: Latest Qemu-COLO Problems

 

Sorry for slow response.

I have fixed this bug in this series:

 

 <https://lists.nongnu.org/archive/html/qemu-devel/2019-02/msg06920.html>
https://lists.nongnu.org/archive/html/qemu-devel/2019-02/msg06920.html

 

Please test it.

 

 

Thanks

Zhang Chen

 

From: wenzt [ <mailto:address@hidden> mailto:address@hidden 
Sent: Friday, February 15, 2019 7:54 PM
To: Zhang, Chen < <mailto:address@hidden> address@hidden>
Cc: 'qemu-discuss' < <mailto:address@hidden>
address@hidden>
Subject: Latest Qemu-COLO Problems

 

Hi Zhang，

 

I have tested COLO with qemu-3.1.0 follow
https://wiki.qemu.org/Features/COLO

 

I got this problems on PVM:

{"timestamp": {"seconds": 1550230616, "microseconds": 644348}, "event":
"STOP"}

{"timestamp": {"seconds": 1550230616, "microseconds": 719003}, "event":
"RESUME"}

{"timestamp": {"seconds": 1550230616, "microseconds": 743554}, "event":
"STOP"}

qemu-system-x86_64: Can't receive COLO message: Input/output error

qemu-system-x86_64: Can't receive COLO message: Input/output error

{"timestamp": {"seconds": 1550230618, "microseconds": 257209}, "event":
"COLO_EXIT", "data": {"mode": "primary", "reason": "error"}}

 

 

And on SVM:

{"timestamp": {"seconds": 1550230616, "microseconds": 731544}, "event":
"STOP"}

address@hidden:colo_vm_state_change
<mailto:address@hidden:colo_vm_state_change>  Change 'run' =>
'stop'

address@hidden:colo_send_message
<mailto:address@hidden:colo_send_message>  Send 'checkpoint-reply'
message

address@hidden:colo_receive_message
<mailto:address@hidden:colo_receive_message>  Receive
'vmstate-send' message

address@hidden:colo_flush_ram_cache_begin <mailto:address@hidden
759522:colo_flush_ram_cache_begin>  dirty_pages 18446744073708498780

address@hidden:colo_flush_ram_cache_end
<mailto:address@hidden:colo_flush_ram_cache_end>  

address@hidden:colo_receive_message Receive 'vmstate-size' message

address@hidden:colo_send_message
<mailto:address@hidden:colo_send_message>  Send 'vmstate-received'
message

{"timestamp": {"seconds": 1550230616, "microseconds": 837436}, "event":
"RESUME"}

qemu-system-x86_64: block.c:5062: bdrv_detach_aio_context: Assertion
`!bs->walking_aio_notifiers' failed.

Aborted (core dumped)