Bug 587501 - [xen] RHEL5.{3,4,5} GA kernel-xen cannot identify large memories(above 32G)
Summary: [xen] RHEL5.{3,4,5} GA kernel-xen cannot identify large memories(above 32G)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen
Version: 5.3
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Xen Maintainance List
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 04:47 UTC by Igor Zhang
Modified: 2010-04-30 08:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-30 07:24:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Igor Zhang 2010-04-30 04:47:37 UTC
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:
1.
2.
3.
  
Actual results:
Only support 32G memory.

Expected results:
Identify all the 128G memory.

Additional info:

Comment 1 Andrew Jones 2010-04-30 07:24:32 UTC
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.