From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MVWsZ-0000NF-Id for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:33:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MVWsV-0000MA-NS for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:33:03 -0400 Received: from [199.232.76.173] (port=37954 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MVWsV-0000M7-KH for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:32:59 -0400 Received: from mx1.redhat.com ([66.187.233.31]:59520) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MVWsU-0003fN-TV for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:32:59 -0400 Date: Mon, 27 Jul 2009 21:32:14 +0100 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Re: virtio-serial: An interface for host-guest communication Message-ID: <20090727203214.GG15020@redhat.com> References: <1248717876-17630-1-git-send-email-amit.shah@redhat.com> <4A6E0C9E.10908@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A6E0C9E.10908@codemonkey.ws> Reply-To: "Daniel P. Berrange" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Amit Shah , qemu-devel@nongnu.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org On Mon, Jul 27, 2009 at 03:22:54PM -0500, Anthony Liguori wrote: > 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 don't think that's not too bad, for example, with fast-user-switching between multiple X servers and/or text consoles, there's already support code that deals with chown'ing things like /dev/snd/* devices to match the active console session. Doing the same with the /dev/vmch3 device so that it is only ever accessible to the current logged in user actually fits in to that scheme quite well. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|