From owner-freebsd-virtualization@FreeBSD.ORG Fri Jun 20 17:52:19 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A499F1E1 for ; Fri, 20 Jun 2014 17:52:19 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 67BCF2A27 for ; Fri, 20 Jun 2014 17:52:19 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 7BBD412420; Sat, 21 Jun 2014 03:52:11 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BVC07087 (AUTH peterg@ptree32.com.au); Sat, 21 Jun 2014 03:52:09 +1000 Message-ID: <53A474C7.9030909@freebsd.org> Date: Fri, 20 Jun 2014 10:52:07 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Cory Smelosky Subject: Re: bhyve: vde2/openvswitch References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org 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 17:52:19 -0000 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.