Date: Mon, 26 Feb 2018 09:50:01 +0900 From: KIRIYAMA Kazuhiko <kiri@kx.openedu.org> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> Cc: tech-lists <tech-lists@zyxst.net>, freebsd-virtualization@freebsd.org Subject: Re: bhyve manager Message-ID: <201802260050.w1Q0o1QE093429@kx.openedu.org> In-Reply-To: <201802251656.w1PGu9gN006097@pdx.rh.CN85.dnsmgr.net> References: <20180225131401.GA3138@v007.zyxst.net> <201802251656.w1PGu9gN006097@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201802260050.w1Q0o1QE093429>