Bug 1624923
| Summary: | [downstream clone - 4.2.6] [PPC64LE] enable memory hotplug support | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
| Component: | ovirt-engine | Assignee: | Michal Skrivanek <michal.skrivanek> |
| Status: | CLOSED ERRATA | QA Contact: | Polina <pagranat> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | bugproxy, bugs, dfodor, dgibson, eheftman, hannsj_uhl, knoel, lsurette, mavital, michal.skrivanek, michen, mshira, mtessun, qzhang, Rhev-m-bugs, srevivo, tburke, virt-bugs, virt-maint, xuhan, xuma |
| Target Milestone: | ovirt-4.2.6 | Keywords: | Automation, ZStream |
| Target Release: | 4.2.6 | ||
| Hardware: | ppc64le | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Memory hotplugging is now available for ppc64le virtual machines.
|
Story Points: | --- |
| Clone Of: | 1284775 | Environment: | |
| Last Closed: | 2018-09-04 13:41:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1284775 | ||
| Bug Blocks: | 1444027 | ||
|
Description
RHV bug bot
2018-09-03 15:20:38 UTC
AFAICT only bug 1282833 is ppc64 specific, the other two appear to be x86 as well. Is that correct? (Originally by David Gibson) 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 (Originally by michal.skrivanek) (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 (Originally by michal.skrivanek) 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 (Originally by michal.skrivanek) moving to 4.0 as the bugs this one depends on are heavily in progress and won't be ready before RHEL 7.3 (Originally by michal.skrivanek) platform side is not ready yet, would need to push this out to 4.1 (Originally by michal.skrivanek) likely need to wait for 7.5 (Originally by michal.skrivanek) should work now with 7.5 (Originally by michal.skrivanek) WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops
(Originally by rhv-bugzilla-bot)
The test was verified by running automation tier1 on ppc9 , version rhv-release-4.2.6-3-001.noarch https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv-4.2-ge-runner-tier1/214/ hotplug memory test cases passed successfully (Originally by Polina Agranat) WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops
(Originally by rhv-bugzilla-bot)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2623 |