Bug 757630 - Max supporting up to more than 4G for 32 bit guests
Summary: Max supporting up to more than 4G for 32 bit guests
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Deadline: 2012-01-06
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: Documentation
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Tahlia Richardson
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 800648 813004 813368
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-28 06:26 UTC by juzhang
Modified: 2014-03-12 07:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-25 06:19:38 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description juzhang 2011-11-28 06:26:52 UTC 
Description of problem:
In
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Hypervisor_Deployment_Guide/References_RHEL_6_RHEVH_Support_Limits_Guests.html

2.2. Guest Requirements and Support Limits
RAM Part

Actual results:
RAM Part
A maximum of 4 GB of virtualized RAM per 32 bit guest is supported. Note that not all 32 bit operating systems are able to register an entire 4 GB of RAM.

Expected results:
About Max support virtualized RAM size per 32 bit guest is more than 4G,it's not static,it's depend on guest itself.for example,about rhel6.2-32 bit guest,I tried install it with 8G using rhevm-3.0.0_0001-40.el6.x86_64.it works.


Additional info:
Comment 1 juzhang 2011-11-28 06:59:10 UTC 
32-bit guest without Physical Address Extension (PAE) support will just show <= 4
GB. with Physical Address Extension (PAE) support will show more than 4G.This
is a hardware limitation, and not a KVM or rhel-m limitation. Max support
virtualized RAM size per 32 bit guest should depend on guest itself
Comment 12 Ronen Hod 2012-06-06 12:15:27 UTC 
Laura,
Yes it is accurate. Thanks, Ronen.
Comment 17 Tahlia Richardson 2013-02-25 06:19:38 UTC 
Closed - this fix is included in the RHEL 6.4 release.
Note You need to log in before you can comment on or make changes to this bug.