From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MVWiu-0005Sh-W2 for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:23:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MVWiq-0005Kr-AR for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:23:04 -0400 Received: from [199.232.76.173] (port=55618 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MVWiq-0005KV-3X for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:23:00 -0400 Received: from wf-out-1314.google.com ([209.85.200.172]:57879) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MVWip-0001sp-Pc for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:22:59 -0400 Received: by wf-out-1314.google.com with SMTP id 26so907406wfd.4 for ; Mon, 27 Jul 2009 13:22:58 -0700 (PDT) Message-ID: <4A6E0C9E.10908@codemonkey.ws> Date: Mon, 27 Jul 2009 15:22:54 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1248717876-17630-1-git-send-email-amit.shah@redhat.com> In-Reply-To: <1248717876-17630-1-git-send-email-amit.shah@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: virtio-serial: An interface for host-guest communication List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org Amit Shah wrote: > Hello all, > > This are the latest version of the patches. > > Lots of things have changed since the last submission. A few of > which I remember: > - VNC copy / paste works* (* conditions apply) > - client vnc copies get propagated to guest port 3 (/dev/vmch3) > - guest writes to port 3 (/dev/vmch3) go straight to client's clipboard > Why 3? Where's the guest application that drives the copy/paste? I expect the first problem you'll run into is that copy/paste daemon has to run as an unprivileged user but /dev/vmch3 is going to be owned by root. You could set udev rules for /dev/vmch3 but that's pretty terrible IMHO. I think you'll find that you need a root daemon that talks to vmchannel and then allows unprivileged connections over a unix socket device. In that case, why even bother having multiple channels since your daemon can multiplex.. Regards, Anthony Liguori