Bug 725484

Summary: kexec-tools: x86: Start using nr_cpus=1 instead of maxcpus=1
Product: Red Hat Enterprise Linux 6 Reporter: Vivek Goyal <vgoyal>
Component: kexec-toolsAssignee: Cong Wang <amwang>
Status: CLOSED ERRATA QA Contact: Chao Ye <cye>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: anderson, caiqian, jburke, jstancek, phan, rkhan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kexec-tools-2_0_0-196_el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 727014 (view as bug list) Environment:
Last Closed: 2011-12-06 18:19:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 717918    
Bug Blocks: 727014    
Attachments:
Description Flags
Proposed patch none

Description Vivek Goyal 2011-07-25 15:32:34 UTC
Description of problem:

Using nr_cpus=1 for kdump kenrel saves memory required in second kernel. Start using that for x86 and x86_64. Do not switch it for powerpc yet as kernel is not equipped to handle that yet.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Vivek Goyal 2011-07-25 15:34:22 UTC
Kernel patches for x86_64 have been committed in version kernel-2.6.32-171.el6. So we should be good to modify kexec-tools now.

Comment 3 Cong Wang 2011-07-26 06:58:27 UTC
Created attachment 515185 [details]
Proposed patch

Comment 4 Cong Wang 2011-07-26 07:21:17 UTC
Brew build:
https://brewweb.devel.redhat.com/taskinfo?taskID=3516689

Comment 6 Chao Ye 2011-09-16 09:05:52 UTC
Tested with Kdump Tier1, no regression found. Change status to VERIFIED.
https://tcms.engineering.redhat.com/run/26802/

Comment 7 errata-xmlrpc 2011-12-06 18:19:30 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/RHSA-2011-1532.html