From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] Re: virtio-serial: An interface for host-guest communication
Date: Thu, 06 Aug 2009 08:58:01 -0500
Message-ID: <4A7AE169.4000606@codemonkey.ws>
References: <4A6E0C9E.10908@codemonkey.ws> <20090727203214.GG15020@redhat.com> <20090727204627.GA32432@shareable.org> <4A6E3BDC.8050101@codemonkey.ws> <20090728140029.GA16067@amd.home.annexia.org> <4A77410D.4090804@codemonkey.ws> <20090805175713.GB28738@shareable.org> <4A79C8D9.5030606@codemonkey.ws> <20090806103843.GC9222@amit-x200.redhat.com> <4A7ADAC4.70902@codemonkey.ws> <20090806134103.GC11733@amit-x200.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jamie Lokier <jamie@shareable.org>,
	virtualization@lists.linux-foundation.org,
	"Richard W.M. Jones" <rjones@redhat.com>, kvm@vger.kernel.org,
	qemu-devel@nongnu.org, Rusty Russell <rusty@rustcorp.com.au>
To: Amit Shah <amit.shah@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-qy0-f196.google.com ([209.85.221.196]:43551 "EHLO
	mail-qy0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755267AbZHFN6E (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 6 Aug 2009 09:58:04 -0400
Received: by qyk34 with SMTP id 34so810700qyk.33
        for <kvm@vger.kernel.org>; Thu, 06 Aug 2009 06:58:05 -0700 (PDT)
In-Reply-To: <20090806134103.GC11733@amit-x200.redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Amit Shah wrote:
> On (Thu) Aug 06 2009 [08:29:40], Anthony Liguori wrote:
>   
>> Amit Shah wrote:
>>     
>>> Sure; but there's been no resistance from anyone from including the
>>> virtio-serial device driver so maybe we don't need to discuss that.
>>>   
>>>       
>> There certainly is from me.  The userspace interface is not reasonable  
>> for guest applications to use.
>>     
>
> One example that would readily come to mind is dbus. A daemon running on
> the guest that reads data off the port and interacts with the desktop by
> appropriate dbus commands. All that's needed is a stream of bytes and
> virtio-serial provides just that.
>   

dbus runs as an unprivileged user, how does dbus know which 
virtio-serial port to open and who sets the permissions on that port?

Regards,

Anthony Liguori