From owner-freebsd-virtualization@FreeBSD.ORG Thu Oct 23 01:24:31 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 029C79F7 for ; Thu, 23 Oct 2014 01:24:31 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E2234F97 for ; Thu, 23 Oct 2014 01:24:30 +0000 (UTC) Received: from u10-2-32-011.office.norse-data.com (unknown [50.204.88.51]) by elvis.mu.org (Postfix) with ESMTPSA id 7B820341F83D for ; Wed, 22 Oct 2014 18:24:29 -0700 (PDT) Message-ID: <544858CD.6020907@freebsd.org> Date: Wed, 22 Oct 2014 18:24:29 -0700 From: Alfred Perlstein Organization: FreeBSD User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: bhyve tapN additions References: <20141022140934.GA367@potato.growveg.org> <20141022141232.36446387.74087.1991@gmail.com> <20141022141631.GB367@potato.growveg.org> <5447C7EB.4060105@freebsd.org> <54482799.8080003@freebsd.org> In-Reply-To: <54482799.8080003@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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: Thu, 23 Oct 2014 01:24:31 -0000 On 10/22/14 2:54 PM, Peter Grehan wrote: > Hi Allan, > >> The tap device can also be created automatically by bhyve, make sure you >> specify a different tap device for each instance of bhyve. > > That may require some devd scripting to get it to be added to a > bridge group. > > We're looking at having the bridge interface have a cloneable > tap-style interface so this step can be avoided i.e. point bhyve at a > /dev/bridgeN device, and it will automatically become a part of that > bridge. Peter, that would be super helpful. Thank you! -Alfred