Yep, I chatted with Allan about this when I first got started. UCL is
definitely the way to go, and I will make that a priority. Though the
current UCL configuration for bhyve is in a state of flux. According to
him, the form is supposed to change quite a bit once bhyve gets support
for some new features (brain fart on which features Peter and Neel
mentioned to Allan). Though, conforming to his form is of course the
right way to proceed. Allan, feel free to chip in and correct me if I am
Agree with you 100% on config file re-use wherever possible. Specially
comes in handy when people want to help and can re-use those files
instead of having to re-define them.
Craig Rodrigues on 11/05/2015 14:59 wrote:
> I would encourage you to use UCL as early as possible. Adding lots of
> command-line options
> to vmrun.sh is doable, but gets a bit clunky.
> I would also encourage you to look at the bhyveucl work done by Allan Jude:
> I think it would be nice if we had a common config file format for bhyve
> based off of UCL.
> That way even if people decide to use their own scripts or utilities,
> at least they can reuse the config files, instead of cobbling together
> their own stuff
> which is overlapping in functionality, but is incompatible.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to