On 16 August 2016 at 10:31, Daniel P. Berrange wrote:
> On Tue, Aug 16, 2016 at 12:33:32PM +0400, Marc-André Lureau wrote:
>> Since commit d7a04fd7d5008, tcp_chr_wait_connected() was introduced,
>> so vhost-user could wait until a backend started successfully. In
>> vhost-user case, the chr socket
Hi
- Original Message -
> On Tue, Aug 16, 2016 at 12:33:32PM +0400, Marc-André Lureau wrote:
> > Since commit d7a04fd7d5008, tcp_chr_wait_connected() was introduced,
> > so vhost-user could wait until a backend started successfully. In
> > vhost-user case, the chr socket must be plain unix
On Tue, Aug 16, 2016 at 12:33:32PM +0400, Marc-André Lureau wrote:
> Since commit d7a04fd7d5008, tcp_chr_wait_connected() was introduced,
> so vhost-user could wait until a backend started successfully. In
> vhost-user case, the chr socket must be plain unix, and the chr+vhost
> setup happens synch
you should push that change - can't find it on http://git.qemu.org/qemu.git
Am 16.08.2016 um 10:33 schrieb Marc-André Lureau:
Since commit d7a04fd7d5008, tcp_chr_wait_connected() was introduced,
so vhost-user could wait until a backend started successfully. In
vhost-user case, the chr socket mus
Since commit d7a04fd7d5008, tcp_chr_wait_connected() was introduced,
so vhost-user could wait until a backend started successfully. In
vhost-user case, the chr socket must be plain unix, and the chr+vhost
setup happens synchronously during qemu startup.
However, with TLS and telnet socket, initial
