This is an interesting question. Funny thing is in the past day I had the same
doubt, but after some minutes I realized FreeBSD already has everything that is
needed to handle a "virtualization network" by itself. Obviously what's missing
is some kind of GUI or guided path to do it easily. At least that's what I
Today I have seen openvswitch site and understood that it has many more
features, but frankly non of them actually raised any interest in me. Maybe I
didn't understand them, but in general id like to jeep things simple, as simple
as possible. And simply put openvswitch seemed to me the next project aimed to
fixing a badly designed tcp stack not working good for many VMs and such. And
after all that's the reason why I'm using FreeBSD and not Linux, and that's
also the reason one of the most powerful networking appliance as pfsense is
based on FreeBSD and not Linux.
So, simply put, instead of spend time adopting something like openvswitch I'd
rather spend time writing something for FreeBSD directly (and maybe merge it
with bhyve project)... But, hey, that's me...
Andrea "Mr.SK" Brancatelli
> On 01/feb/2014, at 10:03, Frédéric Alix <frederic.a...@fredalix.com> wrote:
> Hi !
> I am learning how use bhyve and actullay, it's a real pleasure to use it :-)
> I would like build a virtual infra in a box. Many bhyve vm for each
> services. Firewalls, routers, dns, app serv, databases serv, ...
> For this, bhyve is just perfect.
> Now, i need a tool for build a virtual network, like crossbow in Illumos.
> What are you prefer for this job ? OpenvSwitch ? VDE ? other ?
> Thank you, and long live to bhyve !
> firstname.lastname@example.org mailing list
> To unsubscribe, send any mail to
email@example.com mailing list
To unsubscribe, send any mail to