bhyve clock problem, solved by kern.timecounter.hardware="TSC-low" in /etc/sysctl.conf

[Allan Jude]

On 2015-04-10 14:05, Paul Vixie wrote:
> 
> 
> 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.
> 

I think that was the suggestion, to change the login in timecounter(4)
to detect bhyve (or all virtualization?) and change the quality values
for the different times, so that the best one for the environment
(virtualized, rather than physical) is selected automatically.

Temporarily, as a workaround, /boot/loader.conf is better because it is
applied sooner than /etc/sysctl.conf

-- 
Allan Jude

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-virtualization/attachments/20150410/d95bfd41/attachment.sig>