Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDr. 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:
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 8RHEL 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.
(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
Hello Ani,
As far as I can see, WORKSFORME resolutions are used when the problem described is not a bug and they should not be used for Red Hat Enterprise Linux bugs[1].
In this case, you have provided 3 upstream patches that can solve this bz.
What about changing the resolution to something more appropriate like CURRENTRELEASE?
Thanks!
[1] https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status
(In reply to Mario Casquero from comment #18)
> Hello Ani,
>
> As far as I can see, WORKSFORME resolutions are used when the problem
> described is not a bug and they should not be used for Red Hat Enterprise
> Linux bugs[1].
> In this case, you have provided 3 upstream patches that can solve this bz.
No they are upstream discussion and not patches. I have not pushed any patches upstream and I don't think anything needs fixing for x86_64.
CURRENTRELEASE is fine with me.
> No they are upstream discussion and not patches. I have not pushed any
> patches upstream and I don't think anything needs fixing for x86_64.
> CURRENTRELEASE is fine with me.
My fault, I saw patch word in the title :)
Thanks for updating the resolution!