qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] colo doc problem


From: wang.guang55
Subject: [Qemu-devel] colo doc problem
Date: Fri, 17 Mar 2017 10:13:36 +0800 (CST)

hi


http://git.qemu-project.org/?p=qemu.gita=blobf=docs/COLO-FT.txth=e289be2f419578645475b36861e4303ff624cb0fhb=HEAD




docs/COLO-FT




 138 {'execute':'qmp_capabilities'}

 139 { 'execute': 'nbd-server-start',

 140   'arguments': {'addr': {'type': 'inet', 'data': {'host': 'xx.xx.xx.xx', 
'port': '8889'} } }

 141 }

 142 {'execute': 'nbd-server-add', 'arguments': {'device': 'secondeary-disk0', 
'writable': true } }

secondeary-disk0 should be secondary-disk0 .







thank you.















原始邮件



发件人: address@hidden
收件人:王广10165992
抄送人: address@hidden
日 期 :2017年03月16日 09:24
主 题 :Re: about colo development





Hi,

On 2017/3/15 15:01, address@hidden wrote:
> hi:
> I am testing QEMU COLO feature described here [QEMU 
Wiki](http://wiki.qemu-project.org/Features/COLO).
>
> I found that colo in qemu have not been complete。

Yes, you are right, there are still lots of work need to be done to perfect it.

> Do the have any plan for developing colo?

Sure, I have posted "[PATCH 00/15] COLO: integrate colo frame with block 
replication and net compare"
series, and it is planned to be merged in next version of QEMU. Besides this, 
there are some other
series are on the road.

> How long the colo will be complete for use?

It all depends on the reviewing speed.

> please replay,thank you.
>
>
>
>
>
>
>
> When the Primary Node panic,the Secondary Node qemu hang.
> hang at recvmsg in qio_channel_socket_readv.
> And  I run  { 'execute': 'nbd-server-stop' } and { "execute": 
"x-colo-lost-heartbeat" } in Secondary VM's
> monitor,the  Secondary Node qemu still hang at recvmsg .
>
> Did the recvmsg should be interrupt after failover??
> Has anyone ever run it successfully? Any help is appreciated!
>

We will shutdown the related fd so that it will not be blocked in read/write.
 From your backtrace, it seems that, it didn't go the place call shutdown(fd).

Maybe you need to debug the process of 'x-colo-lost-heartbeat' to figure out 
what happens.

Thanks,
Hailiang

>
>
> centos7.2+qemu2.7.50
> (gdb) bt
> #0  0x00007f3e00cc86ad in recvmsg () from /lib64/libpthread.so.0
> #1  0x00007f3e0332b738 in qio_channel_socket_readv (ioc=<optimized out>, 
iov=<optimized out>, niov=<optimized out>, fds=0x0, nfds=0x0, errp=0x0) at 
io/channel-socket.c:497
> #2  0x00007f3e03329472 in qio_channel_read (address@hidden, address@hidden 
"", address@hidden, address@hidden) at io/channel.c:97
> #3  0x00007f3e032750e0 in channel_get_buffer (opaque=<optimized out>, 
buf=0x7f3e05910f38 "", pos=<optimized out>, size=32768) at 
migration/qemu-file-channel.c:78
> #4  0x00007f3e0327412c in qemu_fill_buffer (f=0x7f3e05910f00) at 
migration/qemu-file.c:257
> #5  0x00007f3e03274a41 in qemu_peek_byte (address@hidden, address@hidden) at 
migration/qemu-file.c:510
> #6  0x00007f3e03274aab in qemu_get_byte (address@hidden) at 
migration/qemu-file.c:523
> #7  0x00007f3e03274cb2 in qemu_get_be32 (address@hidden) at 
migration/qemu-file.c:603
> #8  0x00007f3e03271735 in colo_receive_message (f=0x7f3e05910f00, 
address@hidden) at migration/colo.c:215
> #9  0x00007f3e0327250d in colo_wait_handle_message (errp=0x7f3d62bfaa48, 
checkpoint_request=<synthetic pointer>, f=<optimized out>) at 
migration/colo.c:546
> #10 colo_process_incoming_thread (opaque=0x7f3e067245e0) at 
migration/colo.c:649
> #11 0x00007f3e00cc1df3 in start_thread () from /lib64/libpthread.so.0
> #12 0x00007f3dfc9c03ed in clone () from /lib64/libc.so.6
>
> _____________________________________
> Sent from http://qemu.11.n7.nabble.com
>
>
> .
>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]