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.

Created attachment 1110469 [details]
engine and vdsm logs

Description of problem:
During an attach disk operation of several disks, the vm crashed with "Exit message: "Lost connection with qemu process"

vm kernel: 3.10.0-327.el7.ppc64le


Version-Release number of selected component (if applicable):
rhevm-3.6.1.3-0.1.el6.noarch
rhevm-backend-3.6.1.3-0.1.el6.noarch
vdsm-4.17.13-1.el7ev.noarch
qemu-kvm-tools-rhev-2.3.0-31.el7_2.5.ppc64le
qemu-kvm-common-rhev-2.3.0-31.el7_2.5.ppc64le
qemu-kvm-rhev-2.3.0-31.el7_2.5.ppc64le
qemu-img-rhev-2.3.0-31.el7_2.5.ppc64le


How reproducible:
100%


Steps to Reproduce:
1. Attach several disks to vm in parallel
2.
3.

Actual results:


Expected results:


Additional info:

It seems that after updating the kernel to 3.10.0-327.2.1el7.ppc64le this is not reproducible

Closing based on comment #2

additional info for comment 2:
When host had kernel 3.10.0-327.2.1el7.ppc64le, and VM (guest) had 3.10.0-327.el7.ppc64le this bug occurred. 
After updating VM's kernel to 3.10.0-327.2.1el7.ppc64le, bug didn't reproduced.