This bug was fixed in the package linux-azure - 4.11.0-1009.9
---------------
linux-azure (4.11.0-1009.9) xenial; urgency=low
* linux-azure: 4.11.0-1009.9 -proposed tracker (LP: #1715731)
* [Hyper-V] Read TSC frequency from a synthetic MSR (LP: #1715489)
- x86/hyperv: Check frequency MSRs presence according to the specification
- x86/hyperv: Read TSC frequency from a synthetic MSR
* [Hyper-V] linux-azure: rdma_ucm should autoload on HPC images (LP: #1712915)
- azure: force rdma_ucm to be loaded when hv_network_direct_* is loaded
-- Marcelo Henrique Cerri <marcelo.ce...@canonical.com> Thu, 07 Sep
2017 16:28:39 -0300
** Changed in: linux-azure (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715489
Title:
[Hyper-V] Read TSC frequency from a synthetic MSR
Status in linux package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Confirmed
Status in linux-azure source package in Xenial:
Fix Released
Bug description:
It was found that SMI_TRESHOLD of 50000 is not enough for Hyper-V
guests in nested environment and falling back to counting jiffies
is not an option for Gen2 guests as they don't have PIT. As Hyper-V
provides TSC frequency in a synthetic MSR we can just use this information
instead of doing a error prone calibration.
Upstream commit here:
https://github.com/torvalds/linux/commit/71c2a2d0a81f096a2932fccb39a500116fece554
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715489/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
