| Summary: | mem kernel parameter sets wrong memory size | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Adam Okuliar <aokuliar> |
| Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.8 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-15 12:59:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
mem= refers to the end address of the physical memory on the system, not the amount of memory in the system. Hence with leaving space for the BIOS and PCI devices, you will always see some memory go beyond the 4GB address when you have 4GB installed. This is not a bug |
Description of problem: mem kernel parameter sets wrong memory size Version-Release number of selected component (if applicable): 2.6.18-305.el5 How reproducible: 100% Steps to Reproduce: 1. grab machine from beaker with more than 4096M of memory 2. add mem=4096M to kernel parameters 3. reboot the system Actual results: free -m total used free shared buffers cached Mem: 1970 507 1463 0 32 276 -/+ buffers/cache: 198 1772 Swap: 13983 0 13983 After reboot there is only bit less than 2G available in userspace, although available memory size should be close to 4G. Expected results: mem kernel parameter sets correct memory size Additional info: Discovered on ibm-x3650m3-02.lab.eng.brq.redhat.com