From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bug reports and suggestions
Date: Mon, 8 May 2006 11:58:51 -0400 [thread overview]
Message-ID: <20060508155851.GB15522@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <445BDBF2.9060605@gmx.de>
On Sat, May 06, 2006 at 01:12:50AM +0200, Oliver Gerlich wrote:
> Don Kitchen schrieb:
> > Next, it seems the *one* thing QEMU lacks that you-know-who does correctly
> > is networking, specifically bridged mode. I know about creating a tap device
> > and sticking it into a bridge (really hasn't worked for me, but that's the
> > subject for a different day.) I realize that it's a complicated issue
> > requiring kernel modules, etc, and exponentially more complicated with
> > cross platform, but I wonder if anyone has considered trying to tie into
> > the vmware-player's kernel modules and use them? There has to be some sort
> > of de-facto API for interaction between the modules and the player. Too
> > rife with IP problems?
>
> Someone wrote a kernel module some months ago which exposes some special
> kernel function via /proc ... IIUC this was intended to allow easier
> networking... Does anyone know more about it (or did anyone understand
> my confusing description ;) ?
I'm the author.
It is called vde-inject, and it requires vdeqemu to work atm (though adding
native support in qemu itself is trivial).
Currently I'm working on a version that doesn't require a kernel module to
do this - it will have the limitation of only supporting tcp/ip packets when
talking between host/guest.
>
> Another interesting thing concerning networking: I use a little script
> to set up a bridge between eth0 and tap0; but I have give the new bridge
> interface (eg. br0) an IP address and such stuff, because eth0 doesn't
> work. This is with Linux 2.6, but I read that with Linux 2.4 it was not
> necessary to configure br0, as eth0 would still be accessible. Does
> anyone know why this changed? I think it would be much easier if an
> interface used in a bridge was still usable.
eth0 is still usable. It is just slightly cleaner to use br0 directly.
>
> Thanks,
> Oliver
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
>
> iD8DBQFEW9vwTFOM6DcNJ6cRApc8AJ9qYCEBHJqu/TsWilH5ztnx+PF8wACffVTp
> 2AbeG8IcGxMz3lO1BUeZ3gY=
> =a4mn
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2006-05-08 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 21:51 [Qemu-devel] bug reports and suggestions Don Kitchen
2006-05-05 23:12 ` Oliver Gerlich
2006-05-06 23:03 ` [Qemu-devel] " Anthony Liguori
2006-05-07 5:40 ` wangji
2006-05-08 15:58 ` Jim C. Brown [this message]
2006-05-08 17:05 ` [Qemu-devel] " Oliver Gerlich
2006-05-08 17:28 ` Jim C. Brown
2006-05-06 22:55 ` [Qemu-devel] " Anthony Liguori
2006-05-08 16:17 ` [Qemu-devel] " Jim C. Brown
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=20060508155851.GB15522@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=qemu-devel@nongnu.org \
/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).