Bug 1235403

Summary:	[RFE] Check physical ram addressing limit when hotplugging
Product:	Red Hat Enterprise Linux 8	Reporter:	Dr. David Alan Gilbert <dgilbert>
Component:	qemu-kvm	Assignee:	Ani Sinha <anisinha>
qemu-kvm sub component:	Devices	QA Contact:	Mario Casquero <mcasquer>
Status:	ASSIGNED ---	Docs Contact:
Severity:	low
Priority:	low	CC:	ailan, anisinha, imammedo, jinzhao, juzhang, mdeng, nilal, qzhang, rbalakri, virt-maint, xfu, yuhuang
Version:	8.1	Keywords:	FutureFeature, Improvement, Reopened
Target Milestone:	rc
Target Release:	8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-01 03:02:41 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dr. David Alan Gilbert 2015-06-24 17:32:47 UTC

Description of problem:
Paolo says we don't check the physical addressing limit (36...46 bits etc) when hot adding RAM.  That's probably bad.

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


How reproducible:
Not tried.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Ademar Reis 2020-02-05 22:42:17 UTC

QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

Comment 8 RHEL Program Management 2020-11-01 03:02:41 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 9 Yumei Huang 2020-11-19 02:18:09 UTC

Hi Igor, 

The bug is auto closed. Would you please double check if the issue is not going to be fixed? Otherwise, I guess we need reopen it. Thanks!

Comment 11 Mario Casquero 2023-07-13 08:33:59 UTC

Hello Igor,

Do you still plan to take any action on this bz? Thanks!

Comment 12 Igor Mammedov 2023-07-14 08:12:15 UTC

(In reply to Mario Casquero from comment #11)
> Hello Igor,
> 
> Do you still plan to take any action on this bz? Thanks!

I think Ani plans to look into it he has some spare time

Comment 13 Mario Casquero 2023-07-20 07:24:35 UTC

Hello,

Should we consider include the RFE keyword as this is some kind of 'enhancement'?

Comment 14 Ani Sinha 2023-07-20 07:30:31 UTC

(In reply to Mario Casquero from comment #13)
> Hello,
> 
> Should we consider include the RFE keyword as this is some kind of
> 'enhancement'?

Yes.