Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 587501 - [xen] RHEL5.{3,4,5} GA kernel-xen cannot identify large memories(above 32G)
[xen] RHEL5.{3,4,5} GA kernel-xen cannot identify large memories(above 32G)
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Xen Maintainance List
Red Hat Kernel QE team
Depends On:
  Show dependency treegraph
Reported: 2010-04-30 00:47 EDT by Igor Zhang
Modified: 2010-04-30 04:01 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-30 03:24:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Igor Zhang 2010-04-30 00:47:37 EDT
Description of problem:
My machine(hp-dl785g6-01.rhts.eng.bos.redhat.com) has 128G memories.
But RHEL5.{3,4,5} GA kernel-xen cannot support that large memories. They can only identify 32G.
BTW, RHEL5.2 GA kernel-xen can identify that.
meminfo is from /proc/meminfo.

Version-Release number of selected component (if applicable):
RHEL5.{3,4,5} GA kernel-xen on x86_64

How reproducible:

Steps to Reproduce:
Actual results:
Only support 32G memory.

Expected results:
Identify all the 128G memory.

Additional info:
Comment 1 Andrew Jones 2010-04-30 03:24:32 EDT
dom0 is restricted to 32G by default, with the idea that that is sufficient for most (all) use cases. You can confirm that Xen actually sees all your memory by checking with 'xm info | grep total_memory'. If 32G isn't sufficient for your purposes then you can give it more memory with the xen command line option dom0_mem= 

Check with 'xm info', if it doesn't show what you expect, then you can reopen the bug. Closing as not-a-bug.

Note You need to log in before you can comment on or make changes to this bug.