[Bug 1822821] Re: TSC clocksource not available in nested guests

This bug was fixed in the package linux - 4.4.0-148.174 --- linux (4.4.0-148.174) xenial; urgency=medium * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130 - Documentation/l1tf: Fix small spelling typo - perf/x86/intel: Add model number for Skylake Server to perf -

[Bug 1822821] Re: TSC clocksource not available in nested guests

This bug was fixed in the package linux - 4.15.0-50.54 --- linux (4.15.0-50.54) bionic; urgency=medium * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130 - Documentation/l1tf: Fix small spelling typo - x86/cpu: Sanitize FAM6_ATOM naming - kvm: x86: Report STIBP on

[Bug 1822821] Re: TSC clocksource not available in nested guests

Validated on linux 4.15.0-49.53 from bionic-proposed: ubuntu@bionic-l2:~$ uname -r 4.15.0-49-generic ubuntu@bionic-l2:~$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock tsc hpet acpi_pm ubuntu@bionic-l2:~$ dmesg | grep -i tsc [0.04] tsc: Detected

[Bug 1822821] Re: TSC clocksource not available in nested guests

Validated on linux 4.4.0-147.173 from xenial-proposed: ubuntu@xenial-l2:~$ uname -r 4.4.0-147-generic ubuntu@xenial-l2:~$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock tsc hpet acpi_pm ubuntu@xenial-l2:~$ dmesg | grep -i tsc [0.00] tsc: Detected

[Bug 1822821] Re: TSC clocksource not available in nested guests

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag

[Bug 1822821] Re: TSC clocksource not available in nested guests

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag

[Bug 1822821] Re: TSC clocksource not available in nested guests

** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1822821] Re: TSC clocksource not available in nested guests

Patches submitted to kernel-team list: Xenial - https://lists.ubuntu.com/archives/kernel-team/2019-April/099810.html Bionic - https://lists.ubuntu.com/archives/kernel-team/2019-April/099813.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1822821] Re: TSC clocksource not available in nested guests

** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves) -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1822821] Re: TSC clocksource not available in nested guests

** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822821 Title: TSC clocksource not available in nested guests To manage

[Bug 1822821] Re: TSC clocksource not available in nested guests

This is easily verifiable on both Xenial and Bionic guests from uvt-kvm. I've brought up both as nested instances, and TSC fails to show up as an available clocksource: == Xenial guest == $ uvt-kvm ssh bionic-l1 ubuntu@bionic-l1:~$ uvt-kvm ssh xenial-l2 ubuntu@xenial-l2:~$ uname -r