From owner-freebsd-virtualization@FreeBSD.ORG Mon Jun 23 19:21: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 F11EC2D1; Mon, 23 Jun 2014 19:21:02 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id B37812A21; Mon, 23 Jun 2014 19:21:02 +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 33131126DE; Tue, 24 Jun 2014 05:20:55 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.3.7-GA) with ESMTP id BVI00935 (AUTH peterg@ptree32.com.au); Tue, 24 Jun 2014 05:20:52 +1000 Message-ID: <53A87E12.3050201@freebsd.org> Date: Mon, 23 Jun 2014 12:20:50 -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: Julian Elischer Subject: Re: bhyve: vde2/openvswitch References: <53A474C7.9030909@freebsd.org> <53A79CC9.6080005@freebsd.org> In-Reply-To: <53A79CC9.6080005@freebsd.org> 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: Mon, 23 Jun 2014 19:21:03 -0000 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.