[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] bug reports and suggestions

From: Jim C. Brown
Subject: Re: [Qemu-devel] bug reports and suggestions
Date: Mon, 8 May 2006 11:58:51 -0400
User-agent: Mutt/

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
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> iD8DBQFEW9vwTFOM6DcNJ6cRApc8AJ9qYCEBHJqu/TsWilH5ztnx+PF8wACffVTp
> 2AbeG8IcGxMz3lO1BUeZ3gY=
> =a4mn
> _______________________________________________
> Qemu-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]