02.11.2016 12:39, Markus Armbruster wrote:
> Michael Tokarev writes:
>
>> With current code, pid file is open after various
>> sockets, chardevs, fsdevs and the like. This causes
>> interesting effects, for example when monitor is a
>> unix-socket, and another qemu instance is already
>> running
Michael Tokarev writes:
> With current code, pid file is open after various
> sockets, chardevs, fsdevs and the like. This causes
> interesting effects, for example when monitor is a
> unix-socket, and another qemu instance is already
> running, new qemu first "damages" the socket and
> next com
With current code, pid file is open after various
sockets, chardevs, fsdevs and the like. This causes
interesting effects, for example when monitor is a
unix-socket, and another qemu instance is already
running, new qemu first "damages" the socket and
next complain that it can't acquire the pid fi
