Bug 234325
Summary: | Paravirtualized guest with 90GB of memory crashes system | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Joseph Szczypek <joseph.szczypek> |
Component: | xen | Assignee: | Tetsu Yamamoto <tyamamot> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | martine.silbermann, tyamamot, xen-maint |
Target Milestone: | --- | Keywords: | OtherQA |
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-09-04 14:47:25 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: | |||
Bug Depends On: | |||
Bug Blocks: | 223107 |
Description
Joseph Szczypek
2007-03-28 14:44:32 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Please confirm this behavior with the current 5.1 beta. (In reply to comment #3) > Please confirm this behavior with the current 5.1 beta. If I try to boot a 1VCPU, 90GB PV guest (92160MB) using RHEL5.1 Beta 1 (2.6.18-36.el5xen) on an rx6600 I get the following: pygrub(31875): unaligned access to 0x600000000015110e, ip=0x20000000043b9640 pygrub(31875): unaligned access to 0x6000000000151112, ip=0x20000000043b9150 pygrub(31875): unaligned access to 0x6000000000151114, ip=0x20000000043b9150 pygrub(31875): unaligned access to 0x6000000000151116, ip=0x20000000043b9150 pygrub(31875): unaligned access to 0x600000000015111a, ip=0x20000000043b9150 Error: (4, 'Out of memory', "xc_dom_boot_mem_init: can't allocate low memory for domain\n") I find that I can boot a PV guest if maxmem=memory=65024MB. If I set them to 65536MB, I get the 'Out of memory' error. The system has 96GB of memory, so why can't I create a larger memory guest? Also note that via virt-manager, the max I could increase my PV guest memory size to was 32000MB (the guest was originally installed as a 8GB guest). The system has 96GB in it. I could increase memory beyond 32000MB by editing the config file myself. Please bear in mind that we officially support 64 GB per dom unfortunatelly 65024 MB = 63.5 GB....not quite 64 We actually already have a bug opened about this, and a patch available for 5.2. Closing this as a DUP. Chris Lalancette *** This bug has been marked as a duplicate of 251353 *** Chris, I tried to access 251353 to look at the patch but I'm not authorized. Could you please add me and Joseph Szczypek to the cc list of 251353? Thx - Martine |