Re: bhyve: vde2/openvswitch
Hi Julian, 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. While I don't doubt the utility of being able to hook VMs to netgraph, what I was thinking (hoping) was something like a cloneable tap-like interface to bridge(4) that avoided having to create discrete tap interfaces and bind them to bridge. later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve: vde2/openvswitch
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-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve: vde2/openvswitch
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. 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-unsubscr...@freebsd.org"
Re: bhyve: vde2/openvswitch
On 6/20/14, 8:51 AM, Cory Smelosky wrote: Hey all, Is there any current support for vde2 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? I'm assuming bhyve-to-bhyve network communication is also possible? 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. OpenVSwitch I know less about...but I'm aware it is another virtual switch and it works on FreeBSD...not sure if it has a kernel module or if it's in userspace. With vde2 I know for sure it can be attached to a tap interface and therefore a bridge. 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. ;) 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. I believe it should be possible to plumb up arbitrary vm to vm network topologies using several different schemes, such as running different vms in different vimage jails, and using netgraph as a linkage medium, but I haven't tried them. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
bhyve: vde2/openvswitch
Hey all, Is there any current support for vde2 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? I'm assuming bhyve-to-bhyve network communication is also possible? 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. OpenVSwitch I know less about...but I'm aware it is another virtual switch and it works on FreeBSD...not sure if it has a kernel module or if it's in userspace. With vde2 I know for sure it can be attached to a tap interface and therefore a bridge. 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. ;) 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. -- Cory Smelosky http://gewt.net Personal stuff ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
