On Tue, 15 Jan 2019 at 23:39, Daniel P. Berrangé <berra...@redhat.com> wrote: > > On Fri, Jan 11, 2019 at 04:36:11PM +0800, Yongji Xie wrote: > > On Fri, 11 Jan 2019 at 16:32, Daniel P. Berrangé <berra...@redhat.com> > > wrote: > > > > > > On Fri, Jan 11, 2019 at 03:50:40PM +0800, Yongji Xie wrote: > > > > On Fri, 11 Jan 2019 at 00:41, Daniel P. Berrangé <berra...@redhat.com> > > > > wrote: > > > > > > > > > > We need to fix qemu_chr_fe_wait_connected so that it does explicit > > > > > synchronization wrt to any ongoing background connection process. > > > > > It must only return once all TLS/telnet/websock handshakes have > > > > > completed. If we fix that correctly, then I believe it will also > > > > > solve the problem you're trying to address. > > > > > > > > > > > > > Yes, I think this should be the right way to go. To fix it, my thought > > > > is to track the async QIOChannelSocket in SocketChardev. Then we can > > > > easily get the connection progress in qemu_chr_fe_wait_connected(). Do > > > > you have any suggestion? > > > > > > I've got a few patches that refactor the code to fix this. I'll send them > > > today and CC you on them. > > > > > > > That would be great! Thank you. > > It took me rather longer than expected to fully debug all scenarios, but > I've finally sent patches: > > https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg03344.html >
I will test my series based on this. Thank you. Thanks, Yongji
