Bug 919369

Summary: Wrongly computing MEMSZ
Product: Red Hat Enterprise Linux 5 Reporter: Guangze Bai <gbai>
Component: kexec-toolsAssignee: Baoquan He <bhe>
Status: CLOSED ERRATA QA Contact: Guangze Bai <gbai>
Severity: high Docs Contact:
Priority: urgent    
Version: 5.9CC: ccui, qcai, ruyang, yshao
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: kexec-tools-1.102pre-163.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-30 22:47:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Guangze Bai 2013-03-08 09:30:24 UTC 
Description of problem:

Failed to start kdump on a RHEL5 Xen Domain-0, which has less than 4G RAM:

# uname -r
2.6.18-348.el5xen

# service kdump start
No kdump kernel image found.[WARNING]
Tried to locate /boot/vmlinuz-2.6.18-348.el5PAE
Starting kdump:[FAILED]

Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-348.el5 (i386)
kexec-tools-1.102pre-161.el5 (i386)

How reproducible:
always

Actual results:
Asking for PAE kernel

Expected results:
For <$G system, kdump kernel should be non-PAE. And starting kdump with OK.

Additional info:
Comment 3 Guangze Bai 2013-03-08 09:38:55 UTC 
(In reply to comment #0)
> Expected results:
> For <$G system, kdump kernel should be non-PAE. And starting kdump with OK.
      ^^^
typo, want to say "<4G system"
Comment 4 RHEL Program Management 2013-04-04 12:39:00 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 9 errata-xmlrpc 2013-09-30 22:47:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1321.html