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.

Description of problem:
guest with tpm crashed when executing memory dump to kdump-zlib_format

Version-Release number of selected component (if applicable):
libvirt-8.5.0-5.el9
qemu-kvm-7.0.0-8.el9

How reproducible:
100%

Steps to Reproduce:
1. start a vm with tpm device
...
<tpm model='tpm-crb'>
      <backend type='emulator' version='2.0'/>
    </tpm>
...
2. memory dump
#  virsh dump rhel9 /var/tmp/vm.core --memory-only --format kdump-zlib

Actual results:
error: Failed to core dump domain 'rhel9' to /var/tmp/vm.core
error: operation failed: domain is not running



Expected results:
dump success and vm should not crash.

Additional info:

# virsh domstate rhel9 --reason
shut off (crashed)

# cat rhel9.log
......
qemu-kvm: ../dump/dump.c:1162: _Bool get_next_page(GuestPhysBlock **, uint64_t *, uint8_t **, DumpState *): Assertion `(block->target_start & ~target_page_mask) == 0' failed.
2022-08-23 03:43:00.237+0000: shutting down, reason=crashed
......

The assertion failure comes from qemu, so I'll move the bug to qemu.

For the sake of the qemu team please ideally attach a backtrace of all threads from the crash of the qemu process and the debug log of libvirtd/virtqemud to see the QMP communication.

Hi Zhen,

Would you please help share either the entire xml or the qemu cmdline of your vm? Thanks.

Can be reproduced with upstream qemu too. I am looking for a solution.

Patches on ML:
https://patchew.org/QEMU/20220825132110.1500330-1-marcandre.lureau@redhat.com/

Patches still under review upstream and not committed yet, so reset to ASSIGNED.

Upstream patches merged, moving to POST awaiting upstream qemu-7.2 rebase in December

QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Test pass with qemu-kvm-7.2.0-1.el9,move this bz to verified.Thanks!

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