Date: Fri, 24 Jun 2016 09:22:59 -0400 From: Tycho Nightingale <tycho.nightingale@pluribusnetworks.com> To: Roman Bogorodskiy <bogorodskiy@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve / libvmmapi usage Message-ID: <41CF00F0-06BC-4D48-B52B-92720DF3E0ED@pluribusnetworks.com> In-Reply-To: <20160624130941.GA121@dev.san.ru> References: <20160624130941.GA121@dev.san.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, libvmmapi exists to support bhyveload and bhyve. It's as you say an = internal library. While there is obviously nothing to preclude it=92s = use by others, I wouldn=92t consider it=92s interfaces =93public=94 nor = =93stable=94. Furthermore, though there has been some consideration = taken not to recycle the kernel interface ioctls, I=92d also classify = those interfaces as =93private=94 and =93unstable=94. Tycho On Jun 24, 2016, at 9:09 AM, Roman Bogorodskiy <bogorodskiy@gmail.com> = wrote: > Hi, >=20 > A couple of questions on the libvmmapi lib: >=20 > - Is that a "public" library intended for a wide audience or sort of = an > internal lib to be used by bhyve(8) and friends?=20 > - Somewhat continuation of the first question: any expectations on > libvmmapi API/ABI stability? >=20 > Thanks, >=20 > Roman Bogorodskiy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41CF00F0-06BC-4D48-B52B-92720DF3E0ED>