Date: Tue, 12 Apr 2016 08:34:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards" Message-ID: <bug-208238-27103-1U8WvZzmO4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208238-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-208238-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208238 --- Comment #2 from Dexuan Cui <decui@microsoft.com> --- The tsc-calibration fix was temporarily taken back last Friday because we f= ound an interesting thing: with some kind of config, Xen can pretend to be Hyper= -V by mimicking the hypervisor CPUID signature (this is usually to make Window= s VM run better on Xen), but Xen doesn=E2=80=99t support Hyper-V timecounter, so= the fix causes an unexpected panic when FreeBSD VM runs on Xen in this case. We're making another patch to better detect if the underlying hypervisor supports Hyper-V timecounter or not: https://lists.freebsd.org/pipermail/freebsd-current/2016-April/060519.html --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208238-27103-1U8WvZzmO4>