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 2168187 - [s390x] qemu-kvm coredumps when SE crashes
Summary: [s390x] qemu-kvm coredumps when SE crashes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.8
Hardware: s390x
OS: Linux
medium
medium
Target Milestone: rc
: 8.8
Assignee: Thomas Huth
QA Contact: smitterl
URL:
Whiteboard:
Depends On:
Blocks: 2144443
TreeView+ depends on / blocked
 
Reported: 2023-02-08 12:16 UTC by smitterl
Modified: 2023-05-16 09:00 UTC (History)
7 users (show)

Fixed In Version: qemu-kvm-6.2.0-31.module+el8.8.0+18188+901de023
Doc Type: No Doc Update
Doc Text:
Clone Of: 2168172
Environment:
Last Closed: 2023-05-16 08:18:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/rhel/src/qemu-kvm qemu-kvm merge_requests 260 0 None None None 2023-02-15 09:56:15 UTC
Red Hat Issue Tracker RHELPLAN-147959 0 None None None 2023-02-08 12:18:22 UTC
Red Hat Product Errata RHSA-2023:2757 0 None None None 2023-05-16 08:19:40 UTC

Internal Links: 2168172

Description smitterl 2023-02-08 12:16:45 UTC 
+++ This bug was initially created as a clone of Bug #2168172 +++

Description of problem:
I'm not sure if this is the right component because I cannot reproduce it with the qemu-kvm cli. I am not sure but it looks like the way libvirt creates the machine dump when the vm crashes causes QEMU to coredump


Version-Release number of selected component (if applicable):
qemu-kvm-7.2.0-6.el9.s390x


How reproducible:
100%

Steps to Reproduce:
1. Start a libvirt VM with
  <on_crash>coredump-destroy</on_crash>
  ...
  <launchSecurity type="s390-pv"/>
  (The default machine type will be -rhel9.2.0)
2. Make the VM crash (echo c > /proc/sysrq-trigger, make sure kdump is not running)

Actual results:
a) the machine dump is created
b) qemu-kvm coredumps


Expected results:
b) qemu-kvm doesn't coredump

Additional info:
A) it doesn't reproduce with qemu-kvm-7.1.0-7.el9.s390x and rhel9.0.0 machine type
B) it doesn't reproduce with <on_crash>destroy</on_crash>
C) it coredumps with two different signals:
# coredumpctl
...
Wed 2023-02-08 03:11:49 EST 371477 107 107 SIGSEGV present  /usr/libexec/qemu-kvm 1.6M
Wed 2023-02-08 04:27:13 EST 391483 107 107 SIGABRT present  /usr/libexec/qemu-kvm 2.4M
D) it doesn't reproduce when using a non-secure guest

--- Additional comment from  on 2023-02-08 11:33:02 UTC ---

This was hit by an automated test case that doesn't fail on x86_64 (qemu_conf.auto_dump), hence hw=s390x.

--- Additional comment from  on 2023-02-08 11:34:49 UTC ---

(In reply to smitterl from comment #1)
> This was hit by an automated test case that doesn't fail on x86_64
> (qemu_conf.auto_dump), hence hw=s390x.

Also because it's SE only

--- Additional comment from  on 2023-02-08 11:37:35 UTC ---



--- Additional comment from  on 2023-02-08 12:15:50 UTC ---

I can reproduce this on RHEL 8 with 

qemu-kvm-6.2.0-29.module+el8.8.0+17991+08d03241.s390x


but not with


qemu-kvm-6.2.0-20.module+el8.7.0+16689+53d59bc2.1.s390x.rpm
Comment 6 errata-xmlrpc 2023-05-16 08:18:37 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: virt:rhel and virt-devel:rhel 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:2757
Note You need to log in before you can comment on or make changes to this bug.