Re: [Xen-devel] Re: [PATCH] libxl, Introduce a QMP client

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Tue, Jun 7, 2011 at 15:30, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> wrote:
>> Actually, QEMU doesn't seem to handle more than one client at a time
>> with a single socket.
>
> That seems like a pretty obvious short coming, do you know if it is a
> deliberate policy or just a case of not implemented yet?

I think it because they use the same "char device" code to handle by
example the serial port or the monitor (including QMP). So when a
client is connected, there just stop to handle the listenning fd until
the client disconnects itself.

>>  For more client, we can always open more than
>> one QMP server with different path/port. In this case, they will be
>> handle separately by QEMU.
>
> Problem is determining the correct number to create when we start qemu.

Well, a simple answer would be two, one to listen the event from QEMU,
if we need to do that, and the second one would be for the commands,
one at a time, and libxl close the socket. If a command socket is
already in use, then another libxl client whose trying to connect to
the same socket will wait until QEMU accept the connection.

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel