[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 Dexuan Cui changed: What|Removed |Added Resolution|--- |FIXED

[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 --- Comment #3 from Dexuan Cui --- The further patches on 11-CURRENT should fix the bug safely now: https://github.com/freebsd/freebsd/commit/297e2d2f528a41d9a9614e9b34049801f6935b31

[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 --- Comment #2 from Dexuan Cui --- The tsc-calibration fix was temporarily taken back last Friday because we found an interesting thing: with some kind of config, Xen can pretend to be Hyper-V by mimicking the

[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

Re: calcru runtime went backwards

able to do this. I turned off the Turbo-Boost in the BIOS, and restarted everything. My virtual machine is configured with 4 cpus and 10240 (10GB) of memory. I got the same error today when compiling python in the virtual machine: calcru: runtime went backwards from 48142872748812902 usec

Re: calcru runtime went backwards

Hi Kurt, CPU: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz (2300.13-MHz K8-class CPU) Looks like this Sandy Bridge has turbo-boost. First step is to disable that in the BIOS and see if that has any effect. How many vCPUs in the guest ? later, Peter.