Bug 1692212

Summary:	RHEL6 guest reboot in the destination host after migration finished
Product:	Red Hat Enterprise Linux 8	Reporter:	jingzhao <jinzhao>
Component:	qemu-kvm	Assignee:	Dr. David Alan Gilbert <dgilbert>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	chayang, juzhang, rbalakri, virt-maint, xiaohli, yuhuang
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-31 08:38:24 UTC	Type:	Bug
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:	1691701
Bug Blocks:

Description jingzhao 2019-03-25 02:23:57 UTC

Description of problem:
RHEL6 guest reboot in the destination host after migration finished

Version-Release number of selected component (if applicable):
source host:(rhel8)
destination host:(rhel8)

version:
qemu-kvm-2.12.0-63.module+el8+2833+c7d6d092.x86_64
kernel-4.18.0-80.el8.x86_64

guest: rhel6

How reproducible:
2/2

Steps to Reproduce:
1. Boot guest with qemu command line[1] at source host
   Boot guest with qemu command line[1] with "-incoming tcp:0:5800"

2. In source host:
(qemu) migrate_set_downtime 10
(qemu) migrate_set_speed 1G
(qemu) migrate -d tcp: destination Ip:5800

3. check guest in the destination host after migration finished

Actual results:
RHEL6 guest reboot after migration finished

Expected results:
No reboot after migration finished

Additional info:
[1]
/usr/libexec/qemu-kvm -name rhel6.10 \
-M pc \
-cpu SandyBridge -m 4G \
-smp 4,sockets=1,cores=4,threads=1 \
-device virtio-scsi-pci,id=virtio_scsi_pci0 \
-drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/mnt/rhel610-64-virtio-scsi.qcow2 \
-device scsi-hd,drive=drive_image1,id=image1,bus=virtio_scsi_pci0.0 \
-vnc :2 \
-vga qxl \
-monitor stdio \
-netdev tap,id=hostnet0,vhost=on \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=18:66:da:5f:d1:02 \

Comment 1 Dr. David Alan Gilbert 2019-03-25 19:36:53 UTC

We'll need to confirm but this is probably the same problem as bz 1691701, for now I'll assume it's the same and add a depensdency