Date: Mon, 23 Jun 2014 11:19:37 +0800 From: Julian Elischer <julian@freebsd.org> To: Peter Grehan <grehan@freebsd.org>, Cory Smelosky <b4@gewt.net> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve: vde2/openvswitch Message-ID: <53A79CC9.6080005@freebsd.org> In-Reply-To: <53A474C7.9030909@freebsd.org> References: <alpine.DEB.2.10.1406192041040.12018@melanie> <53A474C7.9030909@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/21/14, 1:52 AM, Peter Grehan wrote: > Hi Cory, >> Is there any current support for vde2 > > None yet. > >> aside from using vde2_plug2tap? >> (Does that even work? I believe vde2 likes to open the tap interface >> exclusively. I need to bring up a bhyve test environment to check >> fully.) > ... >> How exactly does the bhyve network stack work through bridging? I'm >> imaging it's tying in to bridging APIs? > > bhyve uses a tap(4) device. Since that shows up as an ifnet to the > rest of the system, it can be used in any way an ethernet interface > can be used. For bridging, the bridge(4) device is used to join > tap/ethernet interfaces into an L2 bridge. > >> I'm assuming bhyve-to-bhyve network communication is also possible? > > Yes, though currently that is through tap/bridge devices. > >> I can't imagine it'd be too hard to implement vde2 support for >> networking...it'd give me more control over my VMs and give easier >> integration with SIMH VMs. > >> A virtual switch for bhyve would be a useful feature if there >> aren't any >> plans for one. Get up there and have it in base. ;) > > This has been talked about quite a bit, though nothing concrete. Allowing bhyve to talk to netgraph would instantly give this. I think you can already do it by hooking the tap device into the netgraph graph. (I haven't done this for ages bt it used to work) at one time virtual box could also use netgraph for its networking. Not sure if it still can. > >> Unrelated: any plans for a special bhyve-to-bhyve communication bus? >> Not too useful of a feature...I can't think of any use for it off-hand >> aside from dedicating a VM to administrating VMs without exposing much >> to the host beyond configurations. > > There should be code going in soon that allows the netmap VALE > switch to be used for high-speed VM-VM communication. This work also > allows different network back-ends to be written, so it should be a > simple task to drop in a vde2 driver. > > later, > > Peter. > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53A79CC9.6080005>