From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43152)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <a.motakis@virtualopensystems.com>)
	id 1ViiNj-0000Tt-O5
	for qemu-devel@nongnu.org; Tue, 19 Nov 2013 05:18:12 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <a.motakis@virtualopensystems.com>)
	id 1ViiNe-0001AG-E9
	for qemu-devel@nongnu.org; Tue, 19 Nov 2013 05:18:07 -0500
Received: from mail-pd0-f172.google.com ([209.85.192.172]:42152)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <a.motakis@virtualopensystems.com>)
	id 1ViiNe-00018s-98
	for qemu-devel@nongnu.org; Tue, 19 Nov 2013 05:18:02 -0500
Received: by mail-pd0-f172.google.com with SMTP id g10so3553453pdj.3
	for <qemu-devel@nongnu.org>; Tue, 19 Nov 2013 02:18:00 -0800 (PST)
MIME-Version: 1.0
From: Antonios Motakis <a.motakis@virtualopensystems.com>
Date: Tue, 19 Nov 2013 11:17:40 +0100
Message-ID: <CAG8rG2ydBBc2eijDi9GNTPtoe4KtVPF+4zjWEBiO+AeG+eAmaw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Qemu-devel] [RFC] Architecture to connect a userspace ethernet
 switch to QEMU guests via Virtio
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Cc: Luke Gorrie <lukego@gmail.com>, Daniel Raho <s.raho@virtualopensystems.com>

Hello,

There have been discussions before on these lists on the topic of
connecting a QEMU guest running a virtio_net driver, with an external
userspace ethernet switch (Snabbswitch in particular). The essential
requirement in this is to put the virtio backend in the external
userspace process.

The preferred direction should be similar to vhost, with the main
difference of the control mechanism being a unix domain socket instead
of an ioctl interface, and of course placing the backend in an
userspace process instead the kernel.

Since we are pursuing this direction,we would like to share a more
detailed description of the architecture we are working on. Any
feedback is most welcome. It is available here:
http://www.virtualopensystems.com/media/snabbswitch/rfc_snabbswitch_qemu.pdf

Best regards,
Antonios Motakis
Virtual Open Systems