From owner-freebsd-current@freebsd.org Sun Oct 22 08:28:34 2017 Return-Path: Delivered-To: freebsd-current@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 E7F7FE4CB8C; Sun, 22 Oct 2017 08:28:34 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward101o.mail.yandex.net (forward101o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::601]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B82E826BC; Sun, 22 Oct 2017 08:28:34 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback8g.mail.yandex.net (mxback8g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:169]) by forward101o.mail.yandex.net (Yandex) with ESMTP id 0C1E31342875; Sun, 22 Oct 2017 11:28:22 +0300 (MSK) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [2a02:6b8:0:1a2d::28]) by mxback8g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id QlXmCuw6DD-SLr0Wk23; Sun, 22 Oct 2017 11:28:21 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1508660902; bh=oGywilQWzKTcb12LDAoF07lJi5+pL41ukz0b8jZ+SB8=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=SXcAF0mWWsIh5BccT3WbdNl8ZK/9OYHePhuFJoQLevpbxth26B95CixjAcwto7RJ3 WzYkbOY9AKGDGRE99qMqWISDN3zBHA40adgXj51NCyFiLPkPXJ4XnRPtUGGD5zqpZT 5z2iCxWs6OC02Qa5lm2Vn1Ny0JLnQ5bMrLJNDWRQ= Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id dIZPnZo0zk-SKpOU7Yt; Sun, 22 Oct 2017 11:28:21 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1508660901; bh=oGywilQWzKTcb12LDAoF07lJi5+pL41ukz0b8jZ+SB8=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=IDQKtO4tJvKhJYD4QhEKlUJGbrunD9Eisbdf5AE965kSWSBDz6n/+rqwzVgmd55C8 kbwrv6h4kXsqSHAU5mZNmAh4e70/3zVFImqPzvNcqimUcdHLTVxK699jHcu2WYq6+u KGmUuv1mkZr3+HC/1gTJkORAPmMpELPyv29dRoP0= Authentication-Results: smtp4o.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: host, bhyve vm and ntpd To: Michael Voorhis , Ian Lepore Cc: freebsd-current@FreeBSD.org, freebsd-virtualization@FreeBSD.org References: <2931f1cc-6574-b58d-4b94-5f77fa5cdb85@passap.ru> <1508512327.1383.55.camel@freebsd.org> <39bf2426-2edf-d485-7c81-519e931154be@passap.ru> <1508517160.1383.63.camel@freebsd.org> <76ff7afb-3d3a-96f6-1275-89472ff5683d@passap.ru> <1508522667.1383.69.camel@freebsd.org> <30992c14-7b78-ab9f-5693-931e6ca41f1b@passap.ru> <1508523696.1383.75.camel@freebsd.org> <23019.46875.929719.481108@atom.mcvau.net> From: Boris Samorodov Message-ID: <1f33d52f-c087-9cc2-1d88-4f1019ea2c31@passap.ru> Date: Sun, 22 Oct 2017 11:28:20 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <23019.46875.929719.481108@atom.mcvau.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2017 08:28:35 -0000 22.10.2017 00:07, Michael Voorhis пишет: > Ian Lepore writes: >> Beyond that, I'm not sure what else to try.  It might be necessary to >> get some bhyve developers involved (I know almost nothing about it). > > NTPD behaves more normally on uniprocessor VMs. > > A FreeBSD bhyve-guest running on a freebsd host will select a > different timecounter depending on whether it is a multiprocessor or a > uniprocessor. My uniprocessor bhyve-vm selected TSC-low as the best > timecounter in a uniprocessor. NTP functions there as expected. > > kern.timecounter.choice: TSC-low(1000) ACPI-fast(900) HPET(950) i8254(0) dummy(-1000000) > kern.timecounter.hardware: TSC-low > > The very same VM, when given two total CPUs, selected HPET (if I > recall) and the timekeeping with NTPD was unreliable, with many > step-resets to the clock. Yep, the same here. I've switched to TSC-low at Bhyve guest and there is no stepping per 24 hours. -- WBR, bsam