From: wenzt [mailto:[email protected]] Sent: Wednesday, February 27, 2019 6:04 PM To: Zhang, Chen <[email protected]> Cc: 'qemu-discuss' <[email protected]> Subject: 答复: Latest Qemu-COLO Problems
Thanks for help ! I don’t know why we keep switching SVM between Run and Stop ? Why we don’t keep SVM inmigration status ? Because we need do checkpoint to sync all status between PVM and SVM. We can’t guarantee that their status will be the same after a while. Thanks Zhang Chen Thanks, Zhengtao 发件人: Zhang, Chen <[email protected]<mailto:[email protected]>> 发送时间: 2019年2月26日 18:41 收件人: wenzt <[email protected]<mailto:[email protected]>> 抄送: 'qemu-discuss' <[email protected]<mailto:[email protected]>> 主题: 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' <[email protected]<mailto:[email protected]>> Cc: 'qemu-discuss' <[email protected]<mailto:[email protected]>> 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 Please test it. Thanks Zhang Chen From: wenzt [mailto:[email protected]] Sent: Friday, February 15, 2019 7:54 PM To: Zhang, Chen <[email protected]<mailto:[email protected]>> Cc: 'qemu-discuss' <[email protected]<mailto:[email protected]>> 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"} [email protected]:colo_vm_state_change<mailto:[email protected]:colo_vm_state_change> Change 'run' => 'stop' [email protected]:colo_send_message<mailto:[email protected]:colo_send_message> Send 'checkpoint-reply' message [email protected]:colo_receive_message<mailto:[email protected]:colo_receive_message> Receive 'vmstate-send' message [email protected]:colo_flush_ram_cache_begin<mailto:[email protected]:colo_flush_ram_cache_begin> dirty_pages 18446744073708498780 [email protected]:colo_flush_ram_cache_end<mailto:[email protected]:colo_flush_ram_cache_end> [email protected]:colo_receive_message<mailto:[email protected]:colo_receive_message> Receive 'vmstate-size' message [email protected]:colo_send_message<mailto:[email protected]: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)
