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 2077376 - [RFE] Add support for 32-bit guest Windows dump with vmcoreinfo (fwcfg) via 'dump-guest-memory -w'
Summary: [RFE] Add support for 32-bit guest Windows dump with vmcoreinfo (fwcfg) via '...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: leidwang@redhat.com
Jiri Herrmann
URL:
Whiteboard:
Depends On:
Blocks: 1983947
TreeView+ depends on / blocked
 
Reported: 2022-04-21 08:24 UTC by Viktor Prutyanov
Modified: 2023-09-26 14:23 UTC (History)
10 users (show)

Fixed In Version: qemu-kvm-7.1.0-2.el9
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:19:33 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-119473 0 None None None 2022-04-21 08:29:08 UTC
Red Hat Product Errata RHSA-2023:2162 0 None None None 2023-05-09 07:20:28 UTC

Description Viktor Prutyanov 2022-04-21 08:24:37 UTC 
Description of problem:

HMP command 'dump-guest-memory -w' doesn't work for 32-bit guest Windows.

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

How reproducible:
100%

Steps to Reproduce:
1. Run VM with 32-bit Windows
2. Run 'dump-guest-memory -w memory.dmp'

Actual results:
The dump is not produced.

Expected results:
The dump is produced.
Comment 2 Viktor Prutyanov 2022-04-21 08:27:07 UTC 
Upstream patch series v4: https://patchwork.kernel.org/project/qemu-devel/list/?series=629626
Comment 3 Qianqian Zhu 2022-04-22 02:36:27 UTC 
Hi Viktor,

I found that this could be a DUPLICATED with bz 1983947, I am closing it and let's follow bz 1983947 please. Sorry for any inconvenience.

Regards,
Qianqian

*** This bug has been marked as a duplicate of bug 1983947 ***
Comment 4 Qianqian Zhu 2022-04-22 02:38:20 UTC 
Sorry, just noticed this is for qemu not virtio-win driver, moving back now.
Comment 6 Yvugenfi@redhat.com 2022-04-26 10:07:28 UTC 
As the patches were accepted to upstream QEMU after 7.0, moving to RHEL9.2.

https://patchwork.kernel.org/project/qemu-devel/list/?series=629626
Comment 9 Yanan Fu 2022-10-14 02:47:53 UTC 
Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass with the 'Fixed In Version': qemu-kvm-7.1.0-2.el9.
Comment 14 leidwang@redhat.com 2022-10-24 03:14:28 UTC 
Tested it with qemu-kvm-7.1.0-2.el9.x86_64,but dump is not produced.

Env:
kernel-5.14.0-162.6.1.el9_1.x86_64
qemu-kvm-7.1.0-2.el9.x86_64

Steps:
step1:boot up a Win10-32 VM with "-device vmcoreinfo"

step2:install fwcfg driver in VM

step3:(qemu) dump-guest-memory -w memory.dmp
Error: win-dump: failed to read CPU #32 ContextFrame location

Thanks!
Leidong
Comment 15 Yvugenfi@redhat.com 2022-10-25 06:21:32 UTC 
(In reply to leidwang from comment #14)
> Tested it with qemu-kvm-7.1.0-2.el9.x86_64,but dump is not produced.
> 
> Env:
> kernel-5.14.0-162.6.1.el9_1.x86_64
> qemu-kvm-7.1.0-2.el9.x86_64
> 
> Steps:
> step1:boot up a Win10-32 VM with "-device vmcoreinfo"
> 
> step2:install fwcfg driver in VM
> 
> step3:(qemu) dump-guest-memory -w memory.dmp
> Error: win-dump: failed to read CPU #32 ContextFrame location
> 
> Thanks!
> Leidong

Looks related to: https://bugzilla.redhat.com/show_bug.cgi?id=1986665

Please reduce amount of vCPUS for the desktop VM in order to test the current bug.
Comment 16 leidwang@redhat.com 2022-10-26 02:04:08 UTC 
(In reply to Yvugenfi from comment #15)
> (In reply to leidwang from comment #14)
> > Tested it with qemu-kvm-7.1.0-2.el9.x86_64,but dump is not produced.
> > 
> > Env:
> > kernel-5.14.0-162.6.1.el9_1.x86_64
> > qemu-kvm-7.1.0-2.el9.x86_64
> > 
> > Steps:
> > step1:boot up a Win10-32 VM with "-device vmcoreinfo"
> > 
> > step2:install fwcfg driver in VM
> > 
> > step3:(qemu) dump-guest-memory -w memory.dmp
> > Error: win-dump: failed to read CPU #32 ContextFrame location
> > 
> > Thanks!
> > Leidong
> 
> Looks related to: https://bugzilla.redhat.com/show_bug.cgi?id=1986665
> 
> Please reduce amount of vCPUS for the desktop VM in order to test the
> current bug.

Yes,reduce amount of vCPUS and then the dump file is produced.

Move this bz to verified.Thanks!
Comment 20 errata-xmlrpc 2023-05-09 07:19:33 UTC 
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 (Moderate: qemu-kvm security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2162
Note You need to log in before you can comment on or make changes to this bug.