Date: Thu, 16 Aug 2018 18:07:38 +0200 From: "Fabian Freyer" <fabian.freyer@physik.tu-berlin.de> To: "Matt Churchyard" <matt.churchyard@userve.net> Cc: freebsd-virtualization@freebsd.org, novel@FreeBSD.org Subject: Re: Checking bhyve supported features (sysctls) Message-ID: <77D2D821-9132-4AD1-95C1-D2B825E91A6A@physik.tu-berlin.de> In-Reply-To: <3393f8f3d32a4f0890aab87185fbed01@SERVER.ad.usd-group.com> References: <3393f8f3d32a4f0890aab87185fbed01@SERVER.ad.usd-group.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Aug 2018, at 12:16, Matt Churchyard wrote: > I'm looking for better ways to check for bhyve support / available = > features without trying to scan through dmesg output. There=E2=80=99s a few patches floating around for checking features [1,2]= - = however none of these are yet committed. For [2], there=E2=80=99s also an RFC mailing list thread [3]. CC=E2=80=99ing novel@, as he wrote those patches. The hackish way libvirt checks for features right now is to parse error = messages from invalid invocations of bhyve(8). [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210111 [2] https://reviews.freebsd.org/D15992 [3] = https://lists.freebsd.org/pipermail/freebsd-virtualization/2018-June/0065= 36.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77D2D821-9132-4AD1-95C1-D2B825E91A6A>