From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MVWwl-0001sk-9i
	for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:37:23 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MVWwg-0001q7-Aw
	for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:37:22 -0400
Received: from [199.232.76.173] (port=35970 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MVWwg-0001pw-1N
	for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:37:18 -0400
Received: from mail-pz0-f196.google.com ([209.85.222.196]:33746)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MVWwf-0004Tx-LQ
	for qemu-devel@nongnu.org; Mon, 27 Jul 2009 16:37:17 -0400
Received: by pzk34 with SMTP id 34so2148109pzk.4
	for <qemu-devel@nongnu.org>; Mon, 27 Jul 2009 13:37:16 -0700 (PDT)
Message-ID: <4A6E0FF9.6010308@codemonkey.ws>
Date: Mon, 27 Jul 2009 15:37:13 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: virtio-serial: An interface for host-guest
	communication
References: <1248717876-17630-1-git-send-email-amit.shah@redhat.com>
	<4A6E0C9E.10908@codemonkey.ws> <20090727203214.GG15020@redhat.com>
In-Reply-To: <20090727203214.GG15020@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>, qemu-devel@nongnu.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org

Daniel P. Berrange wrote:
> 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.
>   

Yeah, I'm not sure how something like this would interact with f-u-s.

If copy/paste daemon for user foo opens /dev/vmch3 directly, when you 
switch users, how do you forcefully disconnect user foo from /dev/vmch3 
so that user bad can start using it?

Regards,

Anthony Liguori

> Daniel
>