Bug 1672920

Summary: Stress guest and stop it, then do live migration, guest hit call trace on destination end [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: RAD team bot copy to z-stream <autobot-eus-copy>
Component: qemu-kvm-maAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED ERRATA QA Contact: xianwang <xianwang>
Severity: high Docs Contact:
Priority: high    
Version: 7.6-AltCC: mrezanin, qzhang
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-ma-2.12.0-18.el7_6.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1661167 Environment:
Last Closed: 2019-03-13 18:46:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1661167    
Bug Blocks:    

Description RAD team bot copy to z-stream 2019-02-06 08:29:13 UTC
This bug has been copied from bug #1661167 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 2 Miroslav Rezanina 2019-02-06 11:11:19 UTC
Fix included in qemu-kvm-ma-2.12.0-18.el7_6.1

Comment 4 xianwang 2019-02-11 06:12:43 UTC
Bug verify:
Host:
4.14.0-115.5.1.el7a.s390x
qemu-kvm-ma-2.12.0-18.el7_6.1.s390x

Guest:
4.14.0-115.5.1.el7a.s390x

steps:
1.Boot a guest on src end
2.Boot a guest on dst end with incoming mode
3.In guest: execute "stress --cpu 2 --io 2 --vm 2 --vm-bytes 64M" 
4.On src, stop guest and then do live migration
{"execute":"stop"}
{"execute": "migrate", "arguments": {"uri": "tcp:localhost:5801"}}
5.After migration completed, execute "cont" on dst end
{"execute":"cont"}

result:
migration completed and vm works well, no call trace and error.

Comment 6 errata-xmlrpc 2019-03-13 18:46:07 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-2019:0510