From owner-freebsd-fs@freebsd.org  Mon Aug 28 13:26:50 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F481E0D6EA
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 28 Aug 2017 13:26:50 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from mail.in-addr.com (mail.in-addr.com
 [IPv6:2a01:4f8:191:61e8::2525:2525])
 (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 D039777253;
 Mon, 28 Aug 2017 13:26:49 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD))
 (envelope-from <gpalmer@freebsd.org>)
 id 1dmK3z-000LnV-9n; Mon, 28 Aug 2017 14:26:47 +0100
Date: Mon, 28 Aug 2017 14:26:47 +0100
From: Gary Palmer <gpalmer@freebsd.org>
To: Aijaz Baig <aijazbaig1@gmail.com>
Cc: Bakul Shah <bakul@bitblocks.com>, Kirk McKusick <mckusick@mckusick.com>,
 Julian Elischer <julian@freebsd.org>, freebsd-fs@freebsd.org
Subject: Re: Tips on remote debugging for filesystem code
Message-ID: <20170828132647.GA60563@in-addr.com>
References: <CAHB2L+cbBTfT+pvg=c_39EKBSoLAo-_2KdmCcYgURQK5Gio4Xg@mail.gmail.com>
 <201708250251.v7P2pwcl029687@chez.mckusick.com>
 <CAHB2L+crbMGvwAB7zx+naLC5DTbOy7RWbxyFyPCGAZmaLoQ5fg@mail.gmail.com>
 <20170827195428.49400124AE9F@mail.bitblocks.com>
 <CAHB2L+fWd2WBU9GKNK8XGmmwvDTSFRUGChfhxozQ-k8Lj-VPBw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHB2L+fWd2WBU9GKNK8XGmmwvDTSFRUGChfhxozQ-k8Lj-VPBw@mail.gmail.com>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: gpalmer@freebsd.org
X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Aug 2017 13:26:50 -0000

On Mon, Aug 28, 2017 at 01:12:09PM +0530, Aijaz Baig wrote:
> Thanks a lot bakul. Will certain look into this
> 
> Nevertheless I got hold of a PowerEdge 320 system which DOES have a POPCNT
> instruction which shows support for V-x support via EPT but I still get the
> same error there
> 
> sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 2048M -t tap0 -d guest.img -i
> -I FreeBSD-10.3-RELEASE-amd64-bootonly.iso fbsd10
> Launching virtual machine "fbsd10" ...
> vm_create: Device not configured
> 
> dmesg:
> vmx_init: processor does not support VMX operation
> 
> cat /var/run/dmesg.boot | grep -i popcnt
> 
> Features2=0xffba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV>
> 
> Features2=0xffba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV>
> 
> Any ideas?

Hi,

Check the BIOS for virtualisation or other related options.  Some BIOSes have
the ability to turn those features off, even if the processor normally
supports them

Regards,

Gary