From owner-freebsd-virtualization@freebsd.org Mon Aug 28 18:20:30 2017 Return-Path: Delivered-To: freebsd-virtualization@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 B94A4E1186D for ; Mon, 28 Aug 2017 18:20:30 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D25F8361C for ; Mon, 28 Aug 2017 18:20:30 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v7SIKR6k082860; Mon, 28 Aug 2017 11:20:27 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v7SIKRW4082859; Mon, 28 Aug 2017 11:20:27 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201708281820.v7SIKRW4082859@pdx.rh.CN85.dnsmgr.net> Subject: Re: Xeon E5 (PowerEdge 320) bailing out In-Reply-To: <94b9b2e9-676e-e089-2f4c-fd10024ea0e8@nomadlogic.org> To: Pete Wright Date: Mon, 28 Aug 2017 11:20:27 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Mon, 28 Aug 2017 18:20:30 -0000 [ Charset UTF-8 unsupported, converting... ] > > > On 08/28/2017 00:53, Aijaz Baig wrote: > > Trying to run Bhyve on a PowerEdge 320 system which DOES have a POPCNT > > instruction which shows support for VT-x support via EPT but I still get > > the this 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 > SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> > > Features2=0xffba2203 > SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> > > > > Isn't this processor supposed to support Bhyve (Xeon E5)?? > > > > what product number is your E5?? According to the manual you need the > following for Intel CPUs to run bhyve: > > " The easiest way to tell if a processor supports bhyveis to run > |dmesg|or look in |/var/run/dmesg.boot|for...|EPT|and |UG|on the > |VT-x|line for Intel? processors."? (I snipped the reference to POPCNT > which seems to be an AMD only requirement." And POPCNT is not all you need on AMD, there are AMD processors with POPCNT that do not have RIP, and RIP is needed for bhyve, the wiki should be updated to reflect that. > > its possible that your E5 is old enough that it lacks the VT-x support > that bhyve needs. I do not believe there are any XEON e5 class CPUs that lack VT-x, as the E5 family's first versions are Sandy Bridge-EN/EP core based chips. -- Rod Grimes rgrimes@freebsd.org