From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33797)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1btwpw-0007Rz-3K
	for qemu-devel@nongnu.org; Tue, 11 Oct 2016 09:11:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1btwpq-0007uD-S7
	for qemu-devel@nongnu.org; Tue, 11 Oct 2016 09:11:14 -0400
Received: from mx1.redhat.com ([209.132.183.28]:60296)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1btwpq-0007u1-Lk
	for qemu-devel@nongnu.org; Tue, 11 Oct 2016 09:11:10 -0400
Date: Tue, 11 Oct 2016 14:11:07 +0100
From: "Daniel P. Berrange" <berrange@redhat.com>
Message-ID: <20161011131107.GF14917@redhat.com>
Reply-To: "Daniel P. Berrange" <berrange@redhat.com>
References: <20161011102637.GA28347@zurbaran.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20161011102637.GA28347@zurbaran.home>
Subject: Re: [Qemu-devel] Multiple QMP socket clients
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: qemu-devel@nongnu.org

On Tue, Oct 11, 2016 at 12:26:37PM +0200, Samuel Ortiz wrote:
> Hi,
> 
> On a qemu instance started with a qmp unix socket:
> 
> -qmp unix:/tmp/ctrl.sock,server,nowait
> 
> I am trying to have multiple clients working on that socket but
> although the qmp server seems to accept the connections, only the first
> connected client gets his request processed. The next client requests
> will just hang until the first one exits.
> 
> Is that an intended behaviour ?

Yes, the character device code is designed around the idea of a single
endpoint.

In the case of the monitor you could work around it by adding multiple
-qmp arguemnts, each with different socket. Of course you have to make
sure each client doesn't trample on the other client when doing this.


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|