From owner-freebsd-virtualization@freebsd.org Tue Feb 27 15:40:24 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3FFFF30A07 for ; Tue, 27 Feb 2018 15:40:24 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 604E87ECE9 for ; Tue, 27 Feb 2018 15:40:24 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C8ECC21758 for ; Tue, 27 Feb 2018 10:40:23 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 27 Feb 2018 10:40:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=QbxFb4a3xIIzWLnrVMl6WpEHQ7XvM4W/NGVGvY+7zVw=; b=ihqMbMlh clX0cpVvDsAUlONdcagC//yCNX/rz/jrXPMBdPpJ5Vp3aZ1zj2I1RBXuYjbK7f+C EYpNcNng4ALvRyibqHt+g2BngfjCNwES8ymO4tVSVy8cCYloAxMavjB63asU13w3 7m1ZJMq0OeuI0GTnvQyH34FlUv0uq/+u0n7xGfxjjqrkFLYPXgNwjKK2GND0GClU Vp1/SUQ97MZ2Kvet0a48Gn4+kg2Ib0G8oPIkCpEiI8XHRmibjc2x5lZOhqSDoB7I Rq2iBEqzd/vi50LglGqIyPpxglxDBsjDREdBJ2wndEyLHcRmXgxptpp47oHn7XnQ XeTEgdxoeqGyXg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=QbxFb4a3xIIzWLnrVMl6WpEHQ7XvM 4W/NGVGvY+7zVw=; b=HvH554KozywLChawdR+t4ciLSgs4ODDJM6uUQfzLHEHqF JN6Pa4JV8YpzCAsEA4JbrOEaruCvLv/fY1ufIVMpLghkTZdqCm05AZ+k6CvV3E4V TMo2QiaAvKdS7JN2XGVa0yaVB6J/4I0b8uW4dnk6/7o7y/cgnfsbsPvrdY9wWiN0 JYl0W8/M7ht2OPq1Iz47i07K0ywsVcq7lHSFDJxolUUSzIcJ3aSijbjZVbeuKiWA wVC9UVrssbxXYyleBcr7ALF6Ri2QW3f5ybq+LvmaIDkI4GzMi8nZxVxeDlTMmUwZ 68R8+uEMWm++6uixqBNGwGL3kWQf/fKXb30KSdOLw== X-ME-Sender: Received: from v007.zyxst.net (v007.zyxst.net [89.145.100.139]) by mail.messagingengine.com (Postfix) with ESMTPA id 5764D24608 for ; Tue, 27 Feb 2018 10:40:23 -0500 (EST) Date: Tue, 27 Feb 2018 15:40:21 +0000 From: tech-lists To: freebsd-virtualization@freebsd.org Subject: Re: bhyve manager Message-ID: <20180227154021.GA46543@v007.zyxst.net> Mail-Followup-To: freebsd-virtualization@freebsd.org References: <20180225131401.GA3138@v007.zyxst.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20180225131401.GA3138@v007.zyxst.net> User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 27 Feb 2018 15:40:24 -0000 On Sun, Feb 25, 2018 at 01:14:01PM +0000, tech-lists wrote: >Hi, > >What do folks use for their bhyve guest management? > >I have always spun bhyve guests up by hand but now I'm considering >streamlining the process. What do you use? thanks for all the suggestions. I wasn't sure where to start before. Now I know. -- J.