libvmmapi exists to support bhyveload and bhyve.  It's as you say an internal 
library.  While there is obviously nothing to preclude it’s use by others, I 
wouldn’t consider it’s interfaces “public” nor “stable”.  Furthermore, though 
there has been some consideration taken not to recycle the kernel interface 
ioctls, I’d also classify those interfaces as “private” and “unstable”.


On Jun 24, 2016, at 9:09 AM, Roman Bogorodskiy <bogorods...@gmail.com> wrote:

> Hi,
> A couple of questions on the libvmmapi lib:
> - Is that a "public" library intended for a wide audience or sort of an
>  internal lib to be used by bhyve(8) and friends? 
> - Somewhat continuation of the first question: any expectations on
>  libvmmapi API/ABI stability?
> Thanks,
> Roman Bogorodskiy

freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 
  • bhyve / libvmmapi usage Roman Bogorodskiy
    • Re: bhyve / libvmmapi us... Tycho Nightingale via freebsd-virtualization

Reply via email to