Regression: problems migrating recent wily/vivid Xen VMs due to memory hotplug fix
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Vivid |
Fix Released
|
Undecided
|
Unassigned | ||
Wily |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Commit 633d6f17cd91ad5
In my specific case, that 1GB malloc fails as my dom0s aren't big enough, causing all migrations to fail with the migrating VM suspended.
This is fixed in http://
"""
x86/xen/p2m: hint at the last populated P2M entry"
With commit 633d6f17cd91ad5
p2m list for memory hotplug) the P2M may be sized to accomdate a much
larger amount of memory than the domain currently has.
When saving a domain, the toolstack must scan all the P2M looking for
populated pages. This results in a performance regression due to the
unnecessary scanning.
Instead of reporting (via shared_info) the maximum possible size of
the P2M, hint at the last PFN which might be populated. This hint is
increased as new leaves are added to the P2M (in the expectation that
they will be used for populated entries).
Signed-off-by: David Vrabel <email address hidden>
Cc: <email address hidden> # 4.0+
"""
Related branches
CVE References
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: |
added: kernel-da-key removed: vivid |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Vivid): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Wily): | |
status: | New → Fix Committed |
tags: |
added: verification-done-wily removed: verification-needed-wily |
tags: |
added: verification-done-vivid removed: verification-needed-vivid |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1542941
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.