> 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
On 2015-11-04 03:47, Matt Churchyard via freebsd-virtualization 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, indiv
>> 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 infrastr
Going back to the original message in the thread, yes, I think the more the
merrier.
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 a
Well,
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.
Best regards
Andreas
On
On Wednesday, November 04, 2015 09:56:53 PM Andreas Nilsson wrote:
> Well,
>
> 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
