kernel-packages team mailing list archive

[Launchpad Bug Tracker <1552592@xxxxxxxxxxxxxxxxxx>]

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-wily

-- 
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/1552592

Title:
  KVM/QEMU live migration fails with Ubuntu wily kernel 4.2.0-30.35

Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  In Progress
Status in linux-lts-wily source package in Trusty:
  Triaged
Status in linux source package in Wily:
  Fix Committed

Bug description:
  commit 3f11933efc9ef55ecb2ac7e6d626e8d05a99a4b1 - "KVM: x86: expose
  MSR_TSC_AUX to userspace" from ubuntu-wily master git tree breaks
  KVM/QEMU live migration of host with a graphical user interface.

  == Reproduction ==

  Install kernel with 3f11933efc9ef55ecb2ac7e6d626e8d05a99a4b1 included (Ubuntu-4.2.0-30.35)
  Start VM with GUI
  Start migration (no post copy, same migration as you'd in qemu 2.4)
  When migration has finished and you switch the VNC over to the migration target the VM running but frozen showing the last frame buffer, its also not ping-able (so you ssh session is dead if you used that)

  This is independent of (x86_64) Hardware and Guest OS used and also
  the QEMU cpu type (I used mainly kvm64).

  == Backport Solution ==

  After a reverse bisect on the working 4.4 xenial kernel (where it's
  working with the patch from above) I found the missing part.

  While those two KVM patches listed above were backported/added another on was not, namely:
  81b1b9ca6d5ca5f3ce91c0095402def657cf5db3 (from upstream linus)
  KVM: VMX: Fix host initiated access to guest MSR_TSC_AUX
  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=81b1b9ca6d5ca5f3ce91c0095402def657cf5db3

  As there was a API change I made the rather trivial backport to the
  4.2 kernel and tested it successfully.

  The backported patch is attached to this report.

  Some further information and earlier posts from myself about this issue by can be found here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540532
  https://lists.ubuntu.com/archives/kernel-team/2016-March/072356.html

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