From owner-freebsd-virtualization@FreeBSD.ORG Fri Jun 20 02:45:02 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7BB2D13 for ; Fri, 20 Jun 2014 02:45:02 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB7642702 for ; Fri, 20 Jun 2014 02:45:02 +0000 (UTC) Received: from jre-mbp.elischer.org (etroy.elischer.org [121.45.232.70]) (authenticated bits=0) by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s5K2it5m077479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 19 Jun 2014 19:44:59 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <53A3A022.3090004@freebsd.org> Date: Fri, 20 Jun 2014 10:44:50 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Cory Smelosky , freebsd-virtualization@freebsd.org Subject: Re: bhyve: vde2/openvswitch References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2014 02:45:03 -0000 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.