Bug 1346429

Summary:	Include bz1329543 live merge - qemu-kvm hangs in aio_bh_poll - in next RHEV-H release
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marina Kalinin <mkalinin>
Component:	ovirt-node	Assignee:	Douglas Schilling Landgraf <dougsland>
Status:	CLOSED ERRATA	QA Contact:	cshao <cshao>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.6.6	CC:	acanan, ahino, alitke, amureini, bcholler, bmcclain, chayang, cww, dougsland, fdeutsch, gklein, gveitmic, gwatson, huding, jcody, jherrman, juzhang, knoel, lsurette, michal.skrivanek, mkalinin, mkolaja, mst, pax, pezhang, qizhu, rbarry, troels, virt-bugs, virt-maint, xfu, ycui, ykaul, ylavi
Target Milestone:	ovirt-3.6.7	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	During the block-stream job of a live merge operation, the QEMU process in some cases became unresponsive. This update improves the handling of block jobs, which ensures that QEMU stays responsive during block-stream jobs as expected.	Story Points:	---
Clone Of:	1329543	Environment:
Last Closed:	2016-06-29 16:08:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1319400, 1329543
Bug Blocks:

Comment 3 cshao 2016-06-28 06:17:00 UTC

Test version:
rhev-hypervisor7-7.2-20160627.3
qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64
ovirt-node-3.6.1-13.0.el7ev.noarch
vdsm-4.17.31-0.el7ev.noarch
rhevm-3.6.7.5-0.1.el6.noarch

Test steps:
1. Install rhev-h on two machines which have the same cpu type.
2. Register to engine on the same cluster.
3. Connect nfs storage.
4. Create VM.
5. Live migrate.

Test result:
Live migrate can successful, and the correct qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64 package was included into the hypervisor, so the bug is fixed, change bug status to VERIFIED.

Comment 4 errata-xmlrpc 2016-06-29 16:08:46 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, 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/RHBA-2016:1369