From owner-freebsd-virtualization@freebsd.org Wed Sep 30 17:42:09 2015 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 5A843A0BCF1 for ; Wed, 30 Sep 2015 17:42:09 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:1900:2254:206a::19:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx2.freebsd.org", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 460D9162C for ; Wed, 30 Sep 2015 17:42:09 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from hammer.pct.niksun.com (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx2.freebsd.org (Postfix) with ESMTP id E2C3C1BE8; Wed, 30 Sep 2015 17:42:08 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: Re: Re: AMD processors supported under bhyve To: "C. L. Martinez" , "freebsd-virtualization@freebsd.org" References: <560C1AEF.9040202@FreeBSD.org> From: Jung-uk Kim Message-ID: <560C1EF0.9090509@FreeBSD.org> Date: Wed, 30 Sep 2015 13:42:08 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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: Wed, 30 Sep 2015 17:42:09 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/30/2015 13:32, C. L. Martinez wrote: > On Wed, Sep 30, 2015 at 5:25 PM, Jung-uk Kim > wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> On 09/30/2015 12:54, C. L. Martinez wrote: >>> On Tue, Sep 29, 2015 at 11:03 AM, C. L. Martinez >>> wrote: >>>> On Tue, Sep 29, 2015 at 10:43 AM, Jason Tubnor >>>> wrote: >>>>> On 29 September 2015 at 20:07, C. L. Martinez >>>>> wrote: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> Maybe a stupid question, but are AMD processors >>>>>> supported under FreeBSD 10.2-STABLE for bhyve or are they >>>>>> only supported under 11-CURRENT? >>>>> >>>>> >>>>> 10.2-RELEASE is the first release to contain AMD support >>>>> (10.1-STABLE did have support however). 11-CURRENT >>>>> obviously supports it and is where you'll find all the >>>>> latest patches/fixes when reports are made. I use TrueOS >>>>> monthly 11-CURRENT snapshots specifically for this reason >>>>> (and to have binary updates). >>>> >>>> >>>> Thanks Jason... My idea is to use or FreeBSD or HardenedBSD >>>> for this host, and if I have problems maybe I will try TrueOS >>>> ... >>> >>> Uhmm I am installing 10.2-STABLE and I am seeing the following >>> error: >>> >>> module_register_init: MOD_LOAD (vmm, 0xffffffff81d914b0, 0) >>> error 6 >>> >>> Does this means AMD is not supported yet or what?? >> >> We don't support some early generation CPUs. >> >> https://wiki.freebsd.org/bhyve >> >> "Barcelona" class and newer AMD processors include the required >> RVI extension and as with Intel processors, presence of the >> "POPCNT" (POPulation Count) processor feature in dmesg(8) >> indicates RVI support. Note some processors such as Kuma core >> have POPCNT feature but lacks required "NRIPS" (Next RIP Save) >> feature. >> >> Jung-uk Kim > > > Oops .. Thanks Jung-uk. But, is not currently supported for 10.X or > it will never supported? I am asking about using 11-CURRENT. I believe it won't be supported any time soon unless someone is silently working on it. :-( Jung-uk Kim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWDB7sAAoJEHyflib82/FG3MkH/0RepqagWynh4jhivg/xvG8V LnWAYbuPUJ4AtaJwOoeiYVkAeaOYY5IiBPbNfhldltjqoNK3pWlWgvzaVIktznQC UsmIcxAsUQNTGYpvNXLJPTaic+6gC0cMpZvOB6n2RHYZA5A5IhvHYAxDGszAztMa y7i1d7KdE/5T7dWHiZ9rR4VdUbyorBU4y3q85SpuCQsKcZfVNvAw/1eDEOBil6Ys ET2xUoEoRk76FWoG5LyQ1DcVRkk8smw4wXboN1jr47UDHM1750ZcRwEFebU66jLo ONOdxu2ZSQqQDJjJuK3w3Xvn3myw5Vl7QUtoBZ2/UsVzYT/66QFwht6ImqFM7sk= =y65O -----END PGP SIGNATURE-----