From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45226)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VMzMT-00013D-3E
	for qemu-devel@nongnu.org; Fri, 20 Sep 2013 07:59:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VMzMK-0001d0-DK
	for qemu-devel@nongnu.org; Fri, 20 Sep 2013 07:59:00 -0400
Received: from mail-ea0-x230.google.com ([2a00:1450:4013:c01::230]:59337)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VMzMK-0001cX-6Y
	for qemu-devel@nongnu.org; Fri, 20 Sep 2013 07:58:52 -0400
Received: by mail-ea0-f176.google.com with SMTP id q16so205277ead.35
	for <qemu-devel@nongnu.org>; Fri, 20 Sep 2013 04:58:51 -0700 (PDT)
Date: Fri, 20 Sep 2013 13:58:48 +0200
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20130920115848.GC14738@stefanha-thinkpad.redhat.com>
References: <CAPhCscKMbm-YozQsWaww6=fq1=QS3Ewd2ebfvH4hv3yjTDueUQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPhCscKMbm-YozQsWaww6=fq1=QS3Ewd2ebfvH4hv3yjTDueUQ@mail.gmail.com>
Subject: Re: [Qemu-devel] Qemu-KVM VETH
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: Tim Epkes <tim.epkes@gmail.com>
Cc: qemu-devel@nongnu.org

On Thu, Sep 19, 2013 at 05:31:01PM -0400, Tim Epkes wrote:
> Any plans to provide VETH support for Qemu-KVM.  It is a great pt-pt tie
> when when connecting to KVM's on the same machine.  I have multiple reasons
> for doing so (one is educational).  Thanks

QEMU already supports -netdev tap (if you want to use the host Linux
networking stack) and -netdev socket (if you just want point-to-point
tunneling).

The veth driver isn't suitable for QEMU's use case.  QEMU is a userspace
process that wants to inject/extract Ethernet frames.  That's exactly
what the tun (tap) driver does.  veth is useful for containers where you
want a Linux network interface that is handled by the host network stack.

Two solutions for point-to-point:

1. Run two guests with -netdev tap.  Put the interfaces on a software
   bridge (see brctl(8)).  Or you could also use IP forwarding instead
   of a bridge if you like.

2. Run two guests with -netdev socket.  They send Ethernet frames
   directly to each other.

See the qemu man page for configuration details.

Stefan