group.of.nepali.translators team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Adding linux task to show the relationship between the two. Basically
starting with 4.10 the kernel verifies the feature and exposes the
broken implementation.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Trusty)
       Status: New => Invalid

** Changed in: linux (Ubuntu Xenial)
       Status: New => Invalid

** Changed in: linux (Ubuntu Yakkety)
       Status: New => Invalid

** Changed in: linux (Ubuntu Zesty)
       Status: New => Won't Fix

** Changed in: linux (Ubuntu)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1671760

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Triaged

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671760/+subscriptions