From owner-freebsd-virtualization@freebsd.org  Tue Apr 12 08:34:12 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@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 A6310B0BB4F
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Tue, 12 Apr 2016 08:34:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 966961470
 for <freebsd-virtualization@FreeBSD.org>; Tue, 12 Apr 2016 08:34:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3C8YCN3036720
 for <freebsd-virtualization@FreeBSD.org>; Tue, 12 Apr 2016 08:34:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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"
Date: Tue, 12 Apr 2016 08:34:12 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: decui@microsoft.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2016 08:34:12 -0000

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.=