Date: Sun, 25 Feb 2018 17:24:49 +0000 From: Tommi Pernila <tommi.pernila@iki.fi> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Cc: freebsd-virtualization@freebsd.org, tech-lists <tech-lists@zyxst.net> Subject: Re: bhyve manager Message-ID: <CABHD1wQ7PTkert-23kEZmRa76StEi1pQO%2BR0N9=VQOSPmqB=NA@mail.gmail.com> 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
Hi, been happy with sysutils/iohyve https://github.com/pr1ntf/iohyve/blob/master/README.md -T On Sun, 25 Feb 2018 at 19.18, Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> 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 > 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABHD1wQ7PTkert-23kEZmRa76StEi1pQO%2BR0N9=VQOSPmqB=NA>