This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2165917 - qemu-kvm: contrib/elf2dmp: Windows Server 2022 support
Summary: qemu-kvm: contrib/elf2dmp: Windows Server 2022 support
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.2
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Wenkang Ji
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-31 13:20 UTC by Yvugenfi@redhat.com
Modified: 2023-09-20 05:49 UTC (History)
9 users (show)

Fixed In Version: qemu-kvm-8.0.0-11.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 05:49:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5324 0 None Migrated None 2023-09-20 05:48:53 UTC
Red Hat Issue Tracker RHELPLAN-147039 0 None None None 2023-01-31 13:34:29 UTC

Description Yvugenfi@redhat.com 2023-01-31 13:20:18 UTC
Description of problem:
elf2dmp doesn't support converting the qemu guest memory dumps to Windows memory dump format.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yvugenfi@redhat.com 2023-01-31 13:24:37 UTC
Upstream patch: https://www.mail-archive.com/qemu-devel@nongnu.org/msg923837.html

Comment 2 Viktor Prutyanov 2023-02-01 20:33:24 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...

Comment 7 John Ferlan 2023-07-17 19:32:31 UTC
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?

Comment 11 Qianqian Zhu 2023-07-24 08:44:58 UTC
Hi Yan,

DTM is missed, would you please help reset it? Thanks.

Comment 22 Yanan Fu 2023-08-10 11:18:47 UTC
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Comment 38 Viktor Prutyanov 2023-09-02 19:32:54 UTC
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?

Comment 39 Yvugenfi@redhat.com 2023-09-04 07:07:16 UTC
Based on additional issues found in elf2dmp, moving to RHEL9.4

Comment 43 RHEL Program Management 2023-09-20 05:19:48 UTC
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.

Comment 44 RHEL Program Management 2023-09-20 05:49:01 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.