From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaUWj-0007IH-Hz for qemu-devel@nongnu.org; Mon, 10 Aug 2009 09:03:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaUWe-0007GN-En for qemu-devel@nongnu.org; Mon, 10 Aug 2009 09:03:00 -0400 Received: from [199.232.76.173] (port=37202 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaUWe-0007G8-2I for qemu-devel@nongnu.org; Mon, 10 Aug 2009 09:02:56 -0400 Received: from mail-qy0-f174.google.com ([209.85.221.174]:38614) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaUWd-000550-J9 for qemu-devel@nongnu.org; Mon, 10 Aug 2009 09:02:55 -0400 Received: by qyk4 with SMTP id 4so2458003qyk.4 for ; Mon, 10 Aug 2009 06:02:54 -0700 (PDT) Message-ID: <4A801A7B.1020208@codemonkey.ws> Date: Mon, 10 Aug 2009 08:02:51 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: virtio-serial: An interface for host-guest communication 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> In-Reply-To: <4A7FECCA.8080804@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: kvm@vger.kernel.org, "Richard W.M. Jones" , Rusty Russell , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Amit Shah Gerd Hoffmann wrote: > >> There are some other problems with usb too: It's not transparent to >> users. Any hotplug event could alert users and that's not desired. It's >> a system-only thing and should also remain that way. > > I think virtio-serial is the better way to handle vmchannel. Unlike > usb virtio is designed to work nicely in a virtual environment. > > But vmchannel-over-usbserial should be easy too though in case some > guests lacks virtio backports or something. 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 can do the backend over TCP/IP, usb, standard serial, etc. Regards, Anthony Liguori