we need to document the difference from x86 implementation
+++ This bug was initially created as a clone of Bug #1284775 +++
Temporarily disable hotplug memory support until issues (e.g. bug 1282833, bug 1273491, bug 1272742) are sorted out, then enable it:)
+++ This bug was initially created as a clone of Bug #1282833 +++
--- Additional comment from David Gibson on 2015-11-25 00:25:17 CET ---
AFAICT only bug 1282833 is ppc64 specific, the other two appear to be x86 as well. Is that correct?
--- Additional comment from Michal Skrivanek on 2015-11-26 13:41:44 CET ---
so now we have the initial state of hotplug RAM not being enabled on POWER (patch 49072 in the closest to-be-published release).
From now on the bug tracks the required changes (or platform deliverables) to be able to enable it again and match x86 parity as soon as it is deemed stable
--- Additional comment from Michal Skrivanek on 2015-11-26 13:45:55 CET ---
(In reply to David Gibson from comment #1)
> AFAICT only bug 1282833 is ppc64 specific, the other two appear to be x86 as
> well. Is that correct?
right. however there are more situations, now QE run into bug 1285474, which I believe is the same thing about qemu memory hash tables being too large, just this time exposed on migration flow
--- Additional comment from Michal Skrivanek on 2016-02-03 15:21:57 CET ---
we tested that on current 7.2, still problematic (see related bugs), so we are going to keep hotplug disabled for now until the root issue is resolved
--- Additional comment from Michal Skrivanek on 2016-02-08 13:33:08 CET ---
moving to 4.0 as the bugs this one depends on are heavily in progress and won't be ready before RHEL 7.3
This bug has been identified as a tracker for a known issue to be added to the 3.6 Release Notes document. The 'Doc Type' field and 'Doc Text' have been updated accordingly.
This release note has now been published in the Known Issues section of the Release Notes: