On Thu, 6 Dec 2018 at 15:23, Marc-André Lureau <marcandre.lur...@gmail.com> wrote: > > Hi > > On Thu, Dec 6, 2018 at 10:38 AM <elohi...@gmail.com> wrote: > > > > From: Xie Yongji <xieyon...@baidu.com> > > > > Now we attempt to connect asynchronously for "reconnect socket" > > during open(). But vhost-user device prefer a connected socket > > during initialization. That means we may still need to support > > sync connection during open() for the "reconnect socket". > > > > Signed-off-by: Xie Yongji <xieyon...@baidu.com> > > Signed-off-by: Zhang Yu <zhangy...@baidu.com> > > I am not sure this makes much sense, since upon reconnect it won't > "wait" (if I am not mistaken) >
Yes, qemu won't wait when reconnecting. The "wait" here just means that we should wait connection at first time (during open()). I'm not sure whether reuse the "wait" option is OK here. If no this option, current qemu will fail to initialize vhost-user-blk device when "reconnect" option is specified no matter the backend is running or not. Thanks, Yongji
