Bug 2165917
| Summary: | qemu-kvm: contrib/elf2dmp: Windows Server 2022 support | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Yvugenfi <yvugenfi> |
| Component: | qemu-kvm | Assignee: | Yvugenfi <yvugenfi> |
| qemu-kvm sub component: | General | QA Contact: | Wenkang Ji <wji> |
| Status: | CLOSED MIGRATED | Docs Contact: | |
| Severity: | low | ||
| Priority: | medium | CC: | coli, jinzhao, juzhang, kkostiuk, qizhu, viktor, virt-maint, wji, ymankad |
| Version: | 9.2 | Keywords: | MigratedToJIRA, RFE, Triaged |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-8.0.0-11.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-20 05:49:01 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
Yvugenfi@redhat.com
2023-01-31 13:20:18 UTC
Actual result: 4 CPU states has been found CPU #0 CR3 is 0x00000000001ae002 CPU #0 IDT is at 0xfffff80234534000 CPU #0 IDT[0] -> 0xfffff80238a88100 Searching kernel downwards from 0xfffff80238a88000... KernBase = 0xfffff802381fc000, signature is 'MZ' Debug Directory RVA = 0x000048b0 Failed to get PDB symbol store hash Expected result (and result after the patch series as well): 4 CPU states has been found CPU #0 CR3 is 0x00000000001ae002 CPU #0 IDT is at 0xfffff80234534000 CPU #0 IDT[0] -> 0xfffff80238a88100 Searching kernel downwards from 0xfffff80238a88000... KernBase = 0xfffff80238000000, signature is 'MZ' CodeView signature is 'RSDS' PDB name is 'ntkrnlmp.pdb', 'ntkrnlmp.pdb' expected PDB URL is https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/adc00fa5fc34456ba16e2687457240991/ntkrnlmp.pdb % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11.5M 100 11.5M 0 0 1982k 0 0:00:05 0:00:05 --:--:-- 2697k KdDebuggerDataBlock: 0x0000000000c00000(24:'.data') + 0x00000a30 = 0x000c00a30 KdDebuggerDataBlock = 0xfffff80238c00a30 KdVersionBlock: 0x0000000000c00000(24:'.data') + 0x00015508 = 0x000c15508 KdVersionBlock = 0xfffff80238c15508 Filling context for CPU #0... Filling context for CPU #1... Filling context for CPU #2... Filling context for CPU #3... Writing header to file... Upstream fix: https://patchwork.ozlabs.org/project/qemu-devel/patch/20230321132036.1836617-6-peter.maydell@linaro.org/ I see the commit referenced in comment 1 needed to be reworked, create a v2: https://lists.nongnu.org/archive/html/qemu-devel/2023-02/msg06517.html and it seems the commit in comment 5 was merged into qemu-8.0 as: https://gitlab.com/qemu-project/qemu/-/commit/d399d6b179f07b9904de0e76d06c77a3d0a66b51 So can the most recent downstream qemu build be tested so we can work through getting this bug added to the errata for the current release? Hi Yan, DTM is missed, would you please help reset it? Thanks. QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass. Hello, Could you please apply last 4 patches from here: https://github.com/viktor-prutyanov/qemu/commits/elf2dmp-08-2023/contrib/elf2dmp and then build and test elf2dmp again? Based on additional issues found in elf2dmp, moving to RHEL9.4 Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |