Bug 1294778 - [ppc64le] Attaching several disks in parallel will cause "Lost connection with qemu process"
Summary: [ppc64le] Attaching several disks in parallel will cause "Lost connection wit...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.2
Hardware: ppc64le
OS: Unspecified
unspecified
high
Target Milestone: rc
: 7.2
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: RHEV3.6PPC
TreeView+ depends on / blocked
 
Reported: 2015-12-30 10:02 UTC by Raz Tamir
Modified: 2016-02-21 11:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-31 13:49:19 UTC
Target Upstream Version:

Attachments (Terms of Use)
engine and vdsm logs (263.95 KB, application/x-gzip)
2015-12-30 10:02 UTC, Raz Tamir 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Raz Tamir 2015-12-30 10:02:19 UTC 
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:
Comment 2 Raz Tamir 2015-12-30 15:00:23 UTC 
It seems that after updating the kernel to 3.10.0-327.2.1el7.ppc64le this is not reproducible
Comment 3 Gil Klein 2015-12-31 13:49:19 UTC 
Closing based on comment #2
Comment 4 Ilanit Stein 2015-12-31 15:27:42 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.