From owner-freebsd-xen@FreeBSD.ORG Tue Feb 11 17:26:52 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 248AF6BA for ; Tue, 11 Feb 2014 17:26:52 +0000 (UTC) Received: from aslan.scsiguy.com (www.scsiguy.com [70.89.174.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EECA2196F for ; Tue, 11 Feb 2014 17:26:51 +0000 (UTC) Received: from [192.168.6.121] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) (authenticated bits=0) by aslan.scsiguy.com (8.14.7/8.14.7) with ESMTP id s1BHQnYk085382 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 11 Feb 2014 10:26:50 -0700 (MST) (envelope-from gibbs@scsiguy.com) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: FreeBSD 10.0-R as Xen 'guest' - clarification? From: "Justin T. Gibbs" In-Reply-To: <18819F918745D984B618D518@Mail-PC.tdx.co.uk> Date: Tue, 11 Feb 2014 10:26:43 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <7EC86263-B19E-4829-A601-F78DEDCEF7E9@scsiguy.com> References: <18819F918745D984B618D518@Mail-PC.tdx.co.uk> To: Karl Pielorz X-Mailer: Apple Mail (2.1827) Cc: freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 17:26:52 -0000 On Jan 29, 2014, at 8:28 AM, Karl Pielorz = wrote: >=20 > Hi, >=20 > With FreeBSD 10 being out now (Great!) - GENERIC appears now has = everything needed for Xen to run in PVHVM for amd64. >=20 > The man page for xen (man 4 xen) states you should have: >=20 > options NO_ADAPTIVE_MUTEXES > options NO_ADAPTIVE_RWLOCKS > options NO_ADAPTIVE_SX The =93NO_ADAPTIVE=94 settings are an optimization when running in = environments where different guests run on the same physical CPU. = However, many cloud providers seem to statically pin CPUs to VMs, which = means the adaptive lock optimization works as expected. =97 Justin=