From owner-freebsd-virtualization@freebsd.org Mon Feb 26 00:50:08 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 501DDF377F5 for ; Mon, 26 Feb 2018 00:50:08 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 970D679880 for ; Mon, 26 Feb 2018 00:50:06 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w1Q0o1QE093429; Mon, 26 Feb 2018 09:50:02 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201802260050.w1Q0o1QE093429@kx.openedu.org> Date: Mon, 26 Feb 2018 09:50:01 +0900 From: KIRIYAMA Kazuhiko To: "Rodney W. Grimes" Cc: tech-lists , freebsd-virtualization@freebsd.org Subject: Re: bhyve manager In-Reply-To: <201802251656.w1PGu9gN006097@pdx.rh.CN85.dnsmgr.net> References: <20180225131401.GA3138@v007.zyxst.net> <201802251656.w1PGu9gN006097@pdx.rh.CN85.dnsmgr.net> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII 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: Mon, 26 Feb 2018 00:50:08 -0000 At Sun, 25 Feb 2018 08:56:09 -0800 (PST), Rodney W. Grimes 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? > > Personally I use vm-byve with some local hacking on it to remove things MeToo :) vm-bhyve is very simple and intuitive and also easy to modify. I've modified sevral parts as follows: (1) vm image name could be included blanks (2) can be treat with *.img images (3) add force options for destroy or rename I've created vm-bhyve-devel port including above diffs and it's tarball and package were up at [1] and [2]. [1] http://ds.truefc.org/~kiri/freebsd/ports/vm-bhyve-1.2b.tar.gz[ [2] http://ds.truefc.org/~kiri/freebsd/packages/vm-bhyve-devel-1.2b.txz > like 16 character VM names and to allow me to set wired memory from > the config file. Oh, and the CPU output column needs some hackery > after my cpu topology changes as that field can become very wide. > > -- > Rod Grimes rgrimes@freebsd.org > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > --- KIRIYAMA Kazuhiko