Bug 2003830

Summary:	RFE: Support for kdump memory usage estimation via a real crashdump boot cycle
Product:	Red Hat Enterprise Linux 9	Reporter:	Kairui Song <kasong>
Component:	kexec-tools	Assignee:	Lichen Liu <lichliu>
Status:	NEW ---	QA Contact:	Jie Li <jieli>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	9.0	CC:	jieli, ruyang, xiawu, yiyan
Target Milestone:	rc	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-13 07:27:53 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kairui Song 2021-09-13 20:36:47 UTC

Currently `kdumpctl estimate` is based on a hardcoded formula which is based on experience, and calculation based on kernel and initramfs static size. This is incapable of covering all real usage. eg. when a kernel module or userspace program consumes a lot of runtime memory, `kdumpctl estimate` will not provide a reliable value.

A better approach is being worked upstream. `kdumpctl` will trigger a real kernel panic and collect memory usage during the kernel panic dump process. The collected info can help provide a much more reliable memory usage info.

Comment 5 RHEL Program Management 2023-03-13 07:27:53 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.