vmmctl ioctls should have more structure
Currently, the ioctls to create or destroy a bhyve instance pass only a pointer to the name string of the VM as their data argument. This was to mimic the sysctl interface which FreeBSD exposed to VM creation and deletion. As bhyve is built out, it is apparent that when creating an instance, other attributes in addition to the name will be useful to have at create time. Tunable max CPUs, memory allocation strategy, and adjustable VMM capabilities (like APICv) all come to mind as possible additions there. The VMM_CREATE_VM and VMM_DESTROY_VM ioctls should be updated to pass their required data via structures which can be expanded.