Activity log for bug #1542941

Date Who What changed Old value New value Message
2016-02-07 22:01:19 Malcolm Scott bug added bug
2016-02-07 22:30:06 Brad Figg linux (Ubuntu): status New Incomplete
2016-02-07 22:30:09 Brad Figg tags vivid
2016-02-07 22:53:11 Malcolm Scott linux (Ubuntu): status Incomplete Confirmed
2016-02-11 17:45:46 Joseph Salisbury tags vivid kernel-da-key
2016-02-11 17:45:49 Joseph Salisbury linux (Ubuntu): importance Undecided Medium
2016-02-11 18:25:43 penalvch tags kernel-da-key cherry-pick kernel-da-key
2016-02-11 18:25:50 penalvch tags cherry-pick kernel-da-key cherry-pick kernel-da-key reverse-bisect-done
2016-02-11 18:28:32 penalvch description Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka 38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes high resource requirements in the underlying target dom0 (migrating a 64-bit domU involves a 1GB malloc in dom0, as well as a lot of unnecessary work). 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 commit 98dd166ea3a3c3b57919e20d9b0d1237fcd0349d "x86/xen: prepare p2m list for memory hotplug": """ Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear virtual mapped sparse p2m list") introduced a regression regarding to memory hotplug for a pv-domain: as the virtual space for the p2m list is allocated for the to be expected memory size of the domain only, hotplugged memory above that size will not be usable by the domain. Correct this by using a configurable size for the p2m list in case of memory hotplug enabled (default supported memory size is 512 GB for 64 bit domains and 4 GB for 32 bit domains). Signed-off-by: Juergen Gross <jgross@suse.com> Cc: <stable@vger.kernel.org> # 3.19+ Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com> """ Please consider incorporating 98dd166ea3a3c3b57919e20d9b0d1237fcd0349d into the wily and vivid kernels. Thanks. Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka 38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes high resource requirements in the underlying target dom0 (migrating a 64-bit domU involves a 1GB malloc in dom0, as well as a lot of unnecessary work). 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 https://marc.info/?l=git-commits-head&m=142800846201785&w=2 : "x86/xen: prepare p2m list for memory hotplug": """ Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear virtual mapped sparse p2m list") introduced a regression regarding to memory hotplug for a pv-domain: as the virtual space for the p2m list is allocated for the to be expected memory size of the domain only, hotplugged memory above that size will not be usable by the domain. Correct this by using a configurable size for the p2m list in case of memory hotplug enabled (default supported memory size is 512 GB for 64 bit domains and 4 GB for 32 bit domains). Signed-off-by: Juergen Gross <jgross@suse.com> Cc: <stable@vger.kernel.org> # 3.19+ Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com> """ Please consider incorporating 98dd166ea3a3c3b57919e20d9b0d1237fcd0349d into the wily and vivid kernels. Thanks.
2016-02-11 18:28:53 penalvch description Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka 38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes high resource requirements in the underlying target dom0 (migrating a 64-bit domU involves a 1GB malloc in dom0, as well as a lot of unnecessary work). 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 https://marc.info/?l=git-commits-head&m=142800846201785&w=2 : "x86/xen: prepare p2m list for memory hotplug": """ Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear virtual mapped sparse p2m list") introduced a regression regarding to memory hotplug for a pv-domain: as the virtual space for the p2m list is allocated for the to be expected memory size of the domain only, hotplugged memory above that size will not be usable by the domain. Correct this by using a configurable size for the p2m list in case of memory hotplug enabled (default supported memory size is 512 GB for 64 bit domains and 4 GB for 32 bit domains). Signed-off-by: Juergen Gross <jgross@suse.com> Cc: <stable@vger.kernel.org> # 3.19+ Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com> """ Please consider incorporating 98dd166ea3a3c3b57919e20d9b0d1237fcd0349d into the wily and vivid kernels. Thanks. Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka 38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes high resource requirements in the underlying target dom0 (migrating a 64-bit domU involves a 1GB malloc in dom0, as well as a lot of unnecessary work). 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 https://marc.info/?l=git-commits-head&m=142800846201785&w=2 : "x86/xen: prepare p2m list for memory hotplug": """ Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear virtual mapped sparse p2m list") introduced a regression regarding to memory hotplug for a pv-domain: as the virtual space for the p2m list is allocated for the to be expected memory size of the domain only, hotplugged memory above that size will not be usable by the domain. Correct this by using a configurable size for the p2m list in case of memory hotplug enabled (default supported memory size is 512 GB for 64 bit domains and 4 GB for 32 bit domains). Signed-off-by: Juergen Gross <jgross@suse.com> Cc: <stable@vger.kernel.org> # 3.19+ Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com> """
2016-02-11 18:30:00 penalvch linux (Ubuntu): status Confirmed Triaged
2016-02-11 18:39:50 Malcolm Scott description Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka 38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes high resource requirements in the underlying target dom0 (migrating a 64-bit domU involves a 1GB malloc in dom0, as well as a lot of unnecessary work). 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 https://marc.info/?l=git-commits-head&m=142800846201785&w=2 : "x86/xen: prepare p2m list for memory hotplug": """ Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear virtual mapped sparse p2m list") introduced a regression regarding to memory hotplug for a pv-domain: as the virtual space for the p2m list is allocated for the to be expected memory size of the domain only, hotplugged memory above that size will not be usable by the domain. Correct this by using a configurable size for the p2m list in case of memory hotplug enabled (default supported memory size is 512 GB for 64 bit domains and 4 GB for 32 bit domains). Signed-off-by: Juergen Gross <jgross@suse.com> Cc: <stable@vger.kernel.org> # 3.19+ Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com> """ Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka 38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes high resource requirements in the underlying target dom0 (migrating a 64-bit domU involves a 1GB malloc in dom0, as well as a lot of unnecessary work). 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://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=98dd166ea3a3c3b57919e20d9b0d1237fcd0349d : """ x86/xen/p2m: hint at the last populated P2M entry" With commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (x86/xen: prepare 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 <david.vrabel@citrix.com> Cc: <stable@vger.kernel.org> # 4.0+ """
2016-02-11 21:10:27 Tim Gardner nominated for series Ubuntu Wily
2016-02-11 21:10:27 Tim Gardner bug task added linux (Ubuntu Wily)
2016-02-11 21:10:27 Tim Gardner nominated for series Ubuntu Vivid
2016-02-11 21:10:27 Tim Gardner bug task added linux (Ubuntu Vivid)
2016-02-11 21:10:37 Tim Gardner linux (Ubuntu Vivid): status New Fix Committed
2016-02-11 21:10:42 Tim Gardner linux (Ubuntu Wily): status New Fix Committed
2016-02-25 15:54:14 Brad Figg tags cherry-pick kernel-da-key reverse-bisect-done cherry-pick kernel-da-key reverse-bisect-done verification-needed-vivid
2016-02-25 15:54:51 Brad Figg tags cherry-pick kernel-da-key reverse-bisect-done verification-needed-vivid cherry-pick kernel-da-key reverse-bisect-done verification-needed-vivid verification-needed-wily
2016-02-25 17:22:25 Launchpad Janitor branch linked lp:ubuntu/trusty-proposed/linux-lts-vivid
2016-03-01 18:08:31 Malcolm Scott tags cherry-pick kernel-da-key reverse-bisect-done verification-needed-vivid verification-needed-wily cherry-pick kernel-da-key reverse-bisect-done verification-done-wily verification-needed-vivid
2016-03-01 18:23:10 Malcolm Scott tags cherry-pick kernel-da-key reverse-bisect-done verification-done-wily verification-needed-vivid cherry-pick kernel-da-key reverse-bisect-done verification-done-vivid verification-done-wily
2016-03-14 13:14:39 Launchpad Janitor linux (Ubuntu Wily): status Fix Committed Fix Released
2016-03-14 13:14:39 Launchpad Janitor cve linked 2016-2384
2016-03-14 14:01:42 Launchpad Janitor linux (Ubuntu Vivid): status Fix Committed Fix Released