From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [Qemu-devel] Re: virtio-serial: An interface for host-guest communication Date: Mon, 10 Aug 2009 16:02:36 +0200 Message-ID: <4A80287C.7050400@redhat.com> References: <20090805175713.GB28738@shareable.org> <4A79C8D9.5030606@codemonkey.ws> <20090806103843.GC9222@amit-x200.redhat.com> <4A7ADAC4.70902@codemonkey.ws> <20090806134103.GC11733@amit-x200.redhat.com> <4A7AE169.4000606@codemonkey.ws> <20090806140404.GA12083@amit-x200.redhat.com> <20090806173740.GA1178@shareable.org> <20090807063800.GA16769@amit-x200.redhat.com> <4A7C36D3.3040305@codemonkey.ws> <20090810065508.GA4499@amit-x200.redhat.com> <4A7FECCA.8080804@redhat.com> <4A801A7B.1020208@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Amit Shah , kvm@vger.kernel.org, qemu-devel@nongnu.org, Rusty Russell , "Richard W.M. Jones" , virtualization@lists.linux-foundation.org To: Anthony Liguori Return-path: Received: from mx2.redhat.com ([66.187.237.31]:40365 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754813AbZHJODS (ORCPT ); Mon, 10 Aug 2009 10:03:18 -0400 In-Reply-To: <4A801A7B.1020208@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 08/10/09 15:02, Anthony Liguori wrote: > I think you're missing my fundamental point. Don't use the kernel as the > guest interface. > > Introduce a userspace daemon that exposes a domain socket. Then we can > have a proper protocol that uses reverse fqdns for identification. We need nothing but (a) bidirectional byte streams and (b) name tags for them. Do we really want design a daemon and a protocol for such a simple thing? Especially as requiring a daemon for that adds a few problems you don't have without them. Access control for example: For device nodes you can just use standard unix permissions and acls. You can easily do stuff like adding the logged in desktop user to the /dev/vmchannel/org/qemu/clipboard acl using existing solutions. With a daemon you have to hop through a number of loops to archive the same. Can't we simply have guest apps open "/dev/vmchannel/$protocol" ? cheers, Gerd