From owner-freebsd-virtualization@freebsd.org Thu Aug 16 10:17:01 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 1B2CC108525A for ; Thu, 16 Aug 2018 10:17:01 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94A587AAC0 for ; Thu, 16 Aug 2018 10:17:00 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 137F985D for ; Thu, 16 Aug 2018 11:16:53 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1534414613; bh=ND2VL0a8jUvQst+Z9H5LL0mdlxpvBvihTxfeZXIGQBM=; h=From:To:Subject:Date; b=Pzn2wQWJTR78v5DtUka+c8VhEa0OouBPNjPccNT3XrUzXM4pvd4bdVVMHj2DB4hyb L6Y2VnErAcAL48QwB/eImtbnIN8BKoay4O+ZofHIh/0SpPEZHJxU1H/2wNPMEePdiC kgiNwL2ic/BPW48wzgEY3EOdhd3sTHO41vTIfk1w= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Thu, 16 Aug 2018 11:16:52 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Thu, 16 Aug 2018 11:16:52 +0100 From: Matt Churchyard To: "freebsd-virtualization@freebsd.org" Subject: Checking bhyve supported features (sysctls) Thread-Topic: Checking bhyve supported features (sysctls) Thread-Index: AdQ1Sj/JzUfq4S8/RYq4DRXDNWTckQ== Date: Thu, 16 Aug 2018 10:16:52 +0000 Message-ID: <3393f8f3d32a4f0890aab87185fbed01@SERVER.ad.usd-group.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 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 10:17:01 -0000 Hello, I'm looking for better ways to check for bhyve support / available features= without trying to scan through dmesg output. I notice that the following 2 sysctl's appear to be set to 1 as soon as the= vmm module is loaded hw.vmm.vmx.initialized: 1 hw.vmm.vmx.cap.unrestricted_guest: 1 Will these be available on both Intel & AMD processors as a way to determin= e if the module has loaded successfully and can run guests? I also see the below sysctl related to iommu. hw.vmm.iommu.initialized Again, will this be set to 1 as soon as the module is loaded if iommu is su= pported, or only when it is used? There also seems to be a vmm.amdvi.enable sysctl. Would both these need che= cking or is vmm.iommu enough to determine support on any processor. Matt