Bug 1535952

Summary: qemu-kvm-ma differentiation - memory hotplug
Product: Red Hat Enterprise Linux 7 Reporter: Qunfang Zhang <qzhang>
Component: qemu-kvm-maAssignee: Igor Mammedov <imammedo>
Status: CLOSED ERRATA QA Contact: Min Deng <mdeng>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: areis, bugproxy, dgibson, hannsj_uhl, hhuang, imammedo, knoel, lmiksik, michen, mrezanin, mtessun
Target Milestone: rcKeywords: Patch
Target Release: 7.5   
Hardware: ppc64le   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-ma-2.10.0-19.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 14:59:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1399177, 1531672    

Description Qunfang Zhang 2018-01-18 10:19:16 UTC 
Description of problem:

We need differentation patches in qemu-kvm-ma to disable features which are not supported in base RHEL.

This BZ is for memory hotplug.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 7 Miroslav Rezanina 2018-02-02 12:40:57 UTC 
Fix included in qemu-kvm-ma-2.10.0-19.el7
Comment 9 Min Deng 2018-02-05 08:03:46 UTC 
Verified the bug on the following build
qemu-img-ma-2.10.0-19.el7.ppc64le.rpm

Steps,
1.boot up a guest,for example,including the following cli.
 ... -m 20G,maxmem=40G,slots=256...

2.(qemu) object_add memory-backend-ram,id=mem1,size=2G
  (qemu) device_add pc-dimm,id=dimm1,memdev=mem1
  Memory hotplug not supported for this machine

Actual results,the memory hotplug is disabled
Expected results,the memory hotplug is disabled

So this bug should be fixed.Thanks
Comment 12 errata-xmlrpc 2018-04-10 14:59:00 UTC 
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:0831