From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MM2tN-00064S-S0 for qemu-devel@nongnu.org; Wed, 01 Jul 2009 12:42:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MM2tJ-00061R-49 for qemu-devel@nongnu.org; Wed, 01 Jul 2009 12:42:41 -0400 Received: from [199.232.76.173] (port=34531 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MM2tI-00061M-SA for qemu-devel@nongnu.org; Wed, 01 Jul 2009 12:42:36 -0400 Received: from mx2.redhat.com ([66.187.237.31]:34053) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MM2tI-0005b7-Cm for qemu-devel@nongnu.org; Wed, 01 Jul 2009 12:42:36 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n61GgZdg030449 for ; Wed, 1 Jul 2009 12:42:35 -0400 Message-ID: <4A4B91F7.9010206@redhat.com> Date: Wed, 01 Jul 2009 18:42:31 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/2] Tunnel character device data over VNC (v1) References: <20090701162114.GB24296@redhat.com> In-Reply-To: <20090701162114.GB24296@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: qemu-devel@nongnu.org Hi, > The key requirement here is that it should not > be neccessary to specifically configure each character device to make > it available via VNC. The admin should be able to configure the char > devices with all current available backends (file, pty, null, tcp, udp, > unix, etc), and regardless of this config be able to snoop on data from > any active VNC client on demand. Hmm. What is the reason to handle vnc different from unix/tcp/pty/whatever? I would expect something like '-serial vnc,name=foo' here ... cheers, Gerd