Bug 296011
Summary: | Physical Memory swinging up and down by 100 megabytes when there is no physical change to the system. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Sameer Uddin <sameeruj> |
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 5.0 | CC: | byte, luyu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-22 19:57:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sameer Uddin
2007-09-19 09:02:11 UTC
Hm... I thought to get know the first real user of procinfo utility and it's only a misfit bug. This is not for procinfo -- it's for the kernel. Why is this a problem? Just becuase a system doesn't change physical state, doesnt mean we can't change the amount of ram present during the boot process, or after the boot process for that matter. xen dom0 kernels do this to provide system memory to guest kernels. Some arches remove the zero pages from the totalrampage count during boot up since those pages will never be used. It may look a bit funny in your monitoring, but there isn't anything wrong with it. |