Date: Fri, 10 Apr 2015 11:05:02 -0700 From: Paul Vixie <paul@redbarn.org> To: Stephen Stuart <stephen.stuart@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve clock problem, solved by kern.timecounter.hardware="TSC-low" in /etc/sysctl.conf Message-ID: <552810CE.7020502@redbarn.org> In-Reply-To: <CAOb7DXGAWiTUvmq5xJT8Z8W9D3hFuWeHQ-vbADw2AP0Fv4e8Lw@mail.gmail.com> References: <552809F4.6070206@redbarn.org> <CAOb7DXGAWiTUvmq5xJT8Z8W9D3hFuWeHQ-vbADw2AP0Fv4e8Lw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?552810CE.7020502>