Bug 703467
| Summary: | Need an option to retrieve kernel version from vmcore | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Denys Vlasenko <dvlasenk> |
| Component: | crash | Assignee: | Dave Anderson <anderson> |
| Status: | CLOSED ERRATA | QA Contact: | Kernel Dump QE <kernel-dump-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2 | CC: | jmoskovc, phan |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | crash-5.1.7-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
With this update, the new "--osrelease [dump_file]" command line option that displays the OSRELEASE vmcoreinfo string from a kdump dump file has been added.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 16:29:58 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: | 694828 | ||
It would also work on ELF kdumps as well. The only reason that it works with makedumpfile-generated vmcores is because the "vmcoreinfo" ELF note exists in the /proc/vmcore ELF dumpfile, and it gets transferred to the makedumpfile-generated vmcore. It's just not available from "virsh dump" generated kvmdump dumpfiles Ping, any news on this? Since we're going to rebase ABRT in RHEL6.2 we need to provide the new packages before end of July and all features it depends on needs to be available sooner, so we can properly integrate them. It's going to included in the RHEL6.2 crash utility errata. $ file vmcore vmcore: data $ crash --osrelease vmcore 2.6.32-156.el6.x86_64 $ $ file vmcore vmcore: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style $ crash --osrelease vmcore 2.6.32-1.el6.x86_64 $
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
With this update, the new "--osrelease [dump_file]" command line option that displays the OSRELEASE vmcoreinfo string from a kdump dump file has been added.
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-2011-1648.html |
GSS wants to have a way to hook vmcore analysis into abrt. abrt team is working on it. One obstacle in this effort is that in order to process vmcore and extract useful information from it, crash tool needs corresponding debuginfo file. In order to find/download this debuginfo, abrt needs to know the version of crashed kernel which produced vmcore. This information is stored in RHEL6-produced vmcore. We just need a convenient way to extract it. On Wed, 2011-04-27 at 14:23 -0400, Dave Anderson wrote: > > But if the vmcore is an ELF kdump or a makedumpfile-generated > > compressed dumpfile that has vmcoreinfo included (a fairly recent > > innovation, but in RHEL6), then the strings check is totally valid, > > because it shows the OSRELEASE= vmcoreinfo string: > > > > $ strings vmcore | grep OSRELEASE= > > OSRELEASE=2.6.32-15.el6.x86_64 > > $ > > Actually I'm guilty of overstating the need for needing the vmlinux > file *if* the vmcoreinfo OSRELEASE= string is all you need. You could > conceivably do this: > > # crash -d1 vmcore | grep OSRELEASE > OSRELEASE=2.6.32-132.el6.kdump.1.i686 > # > > The -d1 flag will dump the contents of the dumpfile header, > prior to failing because of no vmlinux argument. And amongst > the header contents will be the vmcoreinfo data if it exists. > > It's a bit cleaner than "strings" I suppose... > > But if you wanted to access the actual kernel data structure > containing the OS release data (from which the vmcoreinfo data > string was generated) > I don't need that. What I need it a way to find corresponding kernel debuginfo file for RHEL6-generated vmcore. Not by hand, but with automated code. I don't want to rely on heuristics such as "most likely current kernel is the same one which crashed and generated thus vmcore" - this may be untrue. Similarly, I would rather not use "strings vmcore | grep OSRELEASE=" solution, since it can extract bogus OSRELEASE. Since this information *is* recorded in RHEL6-generated vmcore, I would like a way to fetch it. I am ok with the restriction that it works only on makedumpfile-generated vmcore. Parsing crash -d1 output is not a solution. -d1 is a debugging switch. It may change its format over time. It may change its meaning. It may be removed in later version, for all I know.