From owner-freebsd-virtualization@freebsd.org Thu Aug 16 16:07:59 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D04ED106C398 for ; Thu, 16 Aug 2018 16:07:59 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) Received: from mail.physik.tu-berlin.de (mail.physik-pool.tu-berlin.de [130.149.50.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 654148A6C0; Thu, 16 Aug 2018 16:07:58 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) Received: from [192.168.43.253] (x2f7f27d.dyn.telefonica.de [2.247.242.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.physik.tu-berlin.de (Postfix) with ESMTPSA id 6AF7161FDD; Thu, 16 Aug 2018 16:07:50 +0000 (UTC) From: "Fabian Freyer" To: "Matt Churchyard" Cc: freebsd-virtualization@freebsd.org, novel@FreeBSD.org Subject: Re: Checking bhyve supported features (sysctls) Date: Thu, 16 Aug 2018 18:07:38 +0200 X-Mailer: MailMate (1.11.3r5509) 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 16:08:00 -0000 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