Bug 443618
| Summary: | [REG][Xen][5.2beta] cannot open a vmcore of xen-kdump with crash | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Dave Anderson <anderson> | ||||
| Component: | kernel-xen | Assignee: | Bill Burns <bburns> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.3 | CC: | rlerch, xen-maint | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
crash was unable to read the relocation address of the hypervisor from a vmcore file. Consequently, opening a Virtualized kernel vmcore file with crash would fail, resulting in the error:
crash: cannot resolve "idle_pg_table_4"
In this update, the hypervisor now saves the address correctly, which resolves this issue.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-01-20 19:46:07 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: | 448753, 454962 | ||||||
| Attachments: |
|
||||||
|
Description
Dave Anderson
2008-04-22 15:40:37 UTC
I tried going through the "clone as bug", but I don't see any connection with #BZ 442438. Anyway, this bugzilla exists to track how the RHEL5.2 xen hypervisor, which is now relocated, passes its new "xen_phys_start" value to the vmcore, so that the crash utility will be able to translate virtual addresses to physical addresses, and then to their location in the vmcore. There are 3 bugzillas open to track this issue: crash utility: BZ #442438 [REG][Xen][5.2beta] cannot open a vmcore of xen-kdump with crash https://bugzilla.redhat.com/show_bug.cgi?id=442438 kernel-xen: BZ #443618 [REG][Xen][5.2beta] cannot open a vmcore of xen-kdump with crash https://bugzilla.redhat.com/show_bug.cgi?id=443618 kexec-tools: BZ #443622 [REG][Xen][5.2beta] cannot open a vmcore of xen-kdump with crash https://bugzilla.redhat.com/show_bug.cgi?id=443622 Upstream patch submitted: http://xenbits.xensource.com/xen-unstable.hg?rev/439a3e9459f2 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. Created attachment 309290 [details]
Posted patch.
in kernel-2.6.18-101.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 This bug has been marked for inclusion in the Red Hat Enterprise Linux 5.3 Release Notes. To aid in the development of relevant and accurate release notes, please fill out the "Release Notes" field above with the following 4 pieces of information: Cause: What actions or circumstances cause this bug to present. Consequence: What happens when the bug presents. Fix: What was done to fix the bug. Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Due to a change in the Xen hypervisor the crash utility was unable to open a Xen crash dump. This patch saves the start address so that the crash utility can process the crash dump file. crash was unable to read the relocation address of the hypervisor from a vmcore file. Consequently, opening a Virtualized kernel vmcore file with crash would fail, resulting in the error: crash: cannot resolve "idle_pg_table_4" In this update, the hypervisor now saves the address correctly, which resolves this issue. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,5 @@ -Due to a change in the Xen hypervisor the crash utility was unable to open a Xen crash dump. This patch saves the start address so that the crash utility can process the crash dump file.+crash was unable to read the relocation address of the hypervisor from a vmcore file. Consequently, opening a Virtualized kernel vmcore file with crash would fail, resulting in the error: + +crash: cannot resolve "idle_pg_table_4" + +In this update, the hypervisor now saves the address correctly, which resolves this issue. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-0225.html |