in all honesty, getting vm managers to kvm equivalents ( ie virt-manager )
should not be a goal. virt-manager and friends are terrible. Please
envision something better!
Where it is hosted and what language it is written in doesn't really matter.
Just my 2 cents.
On Wed, Nov 4, 2015 at 4:36 PM, Trent Thompson <trentnthomp...@gmail.com>
> Going back to the original message in the thread, yes, I think the more the
> I created iohyve to solve a problem I had. I wanted to store my bhyve VM's
> in ZFS.
> Matt C. created vm-bhyve to solve the problem of storing VM's in a manager
> that didn't use ZFS.
> Matt and I have traded ideas back and forth even though we maintain
> different managers.
> I think that is the most important thing we need to focus on, working
> together to get bhyve at the same level as KVM and other hypervisors.
> Throw it up on Github so we can prod and poke at it. I don't know much
> about C, but I am always willing to learn.
> -Trent (@pr1ntf)
> On Wed, Nov 4, 2015 at 2:47 AM, Matt Churchyard via freebsd-virtualization
> firstname.lastname@example.org> wrote:
> > > Hello!
> > >
> > > Couple months ago I started writing a bhyve management tool in C for
> > > our startup, in preparation for migration to FreeBSD for our servers.
> > > The goal was to be able to create, drop, and auto-start/stop/restart
> > > VMs, individually or all at once, and provide a plugin infrastructure
> > > to expose some metrics / errors for reporting and aggregation. More
> > > importantly it would detect errors/failures, report them and attempt
> > > to restart the VM per assigned policy.
> > >
> > > The effort stalled due to some high priority work that crept in.
> > > However, I am planning on restarting soon and wanted to check if there
> > > was a need for something like this. I ran across Michael Dexter's
> > > vmrc, and although its shell based, it does provide quite a bit of
> > > features that we were looking for. There's also iohyve. And I heard
> > > Peter and Neel are working on something as well. If there is interest,
> > > this would be open sourced from the start. Or if there is an existing
> > > effort that addresses these problems, I would love to contribute to
> > project.
> > >
> > > Thoughts, comments, concerns, please share.
> > >
> > >vm-bhyve is most mature to this point IME, just don't use the ports
> > version.
> > > Adam
> > Thanks Adam :)
> > I could do with updating the port. Unfortunately this is my first porting
> > experience so not exactly sure of the 'correct' channel to go through to
> > get things updated. It took 2 months for my original port request to be
> > addressed and I'm not sure re-opening that bug is the right way to do it.
> > If anyone uses the port, the error that gets printed when running 'vm
> > init' can be completely ignored. It's just trying to load any existing
> > virtual switches from the switch configuration file, and complaining that
> > the switch configuration file doesn't exist. Apart from that and a few
> > newer features/tweaks, I don't think there's anything particularly
> > show-stopping about the current port/package if people prefer installing
> > that way to downloading from GitHub.
> > Of course it would still be interesting to see a "real" bhyve management
> > tool (possibly even an official one) written in C.
> > Matt
> > _______________________________________________
> > email@example.com mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to "
> > freebsd-virtualization-unsubscr...@freebsd.org"
> firstname.lastname@example.org mailing list
> To unsubscribe, send any mail to "
email@example.com mailing list
To unsubscribe, send any mail to