From: Stefan Hajnoczi <stefanha@gmail.com>
To: Tim Epkes <tim.epkes@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu-KVM VETH
Date: Fri, 20 Sep 2013 13:58:48 +0200 [thread overview]
Message-ID: <20130920115848.GC14738@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAPhCscKMbm-YozQsWaww6=fq1=QS3Ewd2ebfvH4hv3yjTDueUQ@mail.gmail.com>
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
next prev parent reply other threads:[~2013-09-20 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 21:31 [Qemu-devel] Qemu-KVM VETH Tim Epkes
2013-09-20 11:58 ` Stefan Hajnoczi [this message]
2013-09-20 15:48 ` Tim Epkes
2013-09-20 17:26 ` Stefan Hajnoczi
2013-09-20 20:03 ` Tim Epkes
2013-09-24 19:55 ` Tim Epkes
2013-09-25 8:10 ` Stefan Hajnoczi
2013-09-25 11:35 ` Tim Epkes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130920115848.GC14738@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=tim.epkes@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).