KVM/QEMU live migration fails with Ubuntu wily kernel 4.2.0-30.35
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
High
|
Kamal Mostafa | ||
Wily |
Fix Released
|
High
|
Kamal Mostafa | ||
linux-lts-wily (Ubuntu) |
In Progress
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Kamal Mostafa |
Bug Description
commit 3f11933efc9ef55
== Reproduction ==
Install kernel with 3f11933efc9ef55
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:
81b1b9ca6d5ca5f
KVM: VMX: Fix host initiated access to guest MSR_TSC_AUX
https:/
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:/
https:/
Related branches
tags: | added: patch |
Changed in linux (Ubuntu Wily): | |
status: | In Progress → Fix Committed |
Changed in linux-lts-wily (Ubuntu Trusty): | |
status: | In Progress → Triaged |
Changed in linux (Ubuntu Wily): | |
importance: | Undecided → High |
tags: |
added: verification-done-wily removed: verification-needed-wily |
Changed in linux-lts-wily (Ubuntu): | |
assignee: | Kamal Mostafa (kamalmostafa) → nobody |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1552592
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.