From owner-freebsd-virtualization@FreeBSD.ORG Fri Apr 10 18:05:05 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5C256DD for ; Fri, 10 Apr 2015 18:05:05 +0000 (UTC) Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (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 CC0ABD86 for ; Fri, 10 Apr 2015 18:05:05 +0000 (UTC) Received: from [IPv6:2001:559:8000:cb:447:ba78:32f4:47fd] (unknown [IPv6:2001:559:8000:cb:447:ba78:32f4:47fd]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id DA4C518149; Fri, 10 Apr 2015 18:05:03 +0000 (UTC) Message-ID: <552810CE.7020502@redbarn.org> Date: Fri, 10 Apr 2015 11:05:02 -0700 From: Paul Vixie User-Agent: Postbox 3.0.11 (Windows/20140602) MIME-Version: 1.0 To: Stephen Stuart Subject: Re: bhyve clock problem, solved by kern.timecounter.hardware="TSC-low" in /etc/sysctl.conf References: <552809F4.6070206@redbarn.org> In-Reply-To: X-Enigmail-Version: 1.2.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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: Fri, 10 Apr 2015 18:05:06 -0000 Stephen Stuart wrote: > I think the right thing is to set (in /boot/loader.conf) > kern.timecounter.tc.TSC-low.quality to a value higher than that for > HPET, to force the clock choice over what the kernel decides for the > hardware that you're running on. See timecounters(4). if every bhyve guest ever is going to need this, then the interface offered to the guest kernel ought to present the right set of defaults to cause the right choice to be made, or the guest kernel must simply "know better". in other words me adding something to /boot/loader.conf or /etc/sysctl.conf in every single bhyve guest ever is an indication that we're doing something wrong elsewhere. -- Paul Vixie