Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
(In reply to Dr. David Alan Gilbert from comment #3)
> 1) Can you try with a different NIC than e1000e - I'm tracking a separate
> e1000e migration bug
Try with "virtio-net-pci", can not reproduce.
> 2) Does a Linux guest fail in the same way?
Not fail in the same way.
Comment 5Dr. David Alan Gilbert
2017-05-11 10:30:46 UTC
(In reply to xiagao from comment #4)
> (In reply to Dr. David Alan Gilbert from comment #3)
> > 1) Can you try with a different NIC than e1000e - I'm tracking a separate
> > e1000e migration bug
> Try with "virtio-net-pci", can not reproduce.
Hmm in that case I wonder if it's related to bz 1447935 that's a windows migrate problem with e1000e.
> > 2) Does a Linux guest fail in the same way?
> Not fail in the same way.
Comment 6Dr. David Alan Gilbert
2017-05-11 11:51:44 UTC
when you say 'guest hang' is it completely hung? Does the mouse still move?
On bz 1447935 the mouse still moves, just nothing else happens - or if it does happen it happens very slowly.
(My suspicion is the network card is giving out lots and lots of false interrupts so the guest gets nothing else done)
(In reply to Dr. David Alan Gilbert from comment #6)
> when you say 'guest hang' is it completely hung? Does the mouse still move?
> On bz 1447935 the mouse still moves, just nothing else happens - or if it
> does happen it happens very slowly.
>
>
> (My suspicion is the network card is giving out lots and lots of false
> interrupts so the guest gets nothing else done)
Hi, in my test environment the guest is completely hung and the mouse can not move.
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/RHSA-2017:2392
Description of problem: guest hang after do migration with scsi controller under q35 Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.9.0-3.el7.x86_64 kernel-3.10.0-663.el7.x86_64 OVMF-20170228-4.gitc325e41585e3.el7.noarch How reproducible: 3/3 Steps to Reproduce: 1. boot guest with qemu cmd line [1] 2. start dst guest with “-incoming tcp:0:5800 ” 3. doing live migration to dst host {"execute": "migrate","arguments":{"uri": "tcp:0:5800"}} 4. after migration,check guest Actual results: guest hang. Expected results: guest runs well. Additional info: [1]: /usr/libexec/qemu-kvm \ -name 'win10-64-scsi-ovmf-nfs' \ -nodefaults \ -vga std \ -m 3G \ -smp 4 \ -enable-kvm \ -usb -device usb-tablet \ -machine q35,smm=on,accel=kvm \ -drive file=/usr/share/OVMF/OVMF_CODE.secboot.fd,if=pflash,format=raw,readonly=on,unit=0 \ -drive file=/home/OVMF_VARS_xiagao22.fd,if=pflash,format=raw,unit=1 \ -debugcon file:/home/ovmf.log \ -global isa-debugcon.iobase=0x402 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cd,menu=on \ -vnc :1 \ -enable-kvm \ -monitor stdio \ -qmp tcp:0:1235,server,nowait \ -device ahci,id=ahci \ -drive file=virtio-win-prewhql-136.vfd,if=floppy,id=drive-fdc0-0-0,format=raw,cache=none \ -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000e,netdev=hostnet0,id=net0,mac=00:52:0a:5c:f2:1a \ -device ioh3420,bus=pcie.0,id=root1.0,slot=1 -device virtio-scsi-pci,id=scsi0,num_queues=4,bus=root1.0 \ -drive file=win1064.ovmf,if=none,id=drive-scsi-disk0,format=raw,serial=xiagao,cache=none -device scsi-hd,bus=scsi0.0,drive=drive-scsi-disk0,id=scsi-disk0 \ -device ioh3420,bus=pcie.0,id=root2.0,slot=2 -device virtio-scsi-pci,id=scsi1,num_queues=4,bus=root2.0 \ -drive file=scsi-disk3.raw,if=none,id=drive-scsi-disk1,format=raw,serial=xiagao123,cache=none -device scsi-hd,bus=scsi1.0,drive=drive-scsi-disk1,id=scsi-disk1 \ -device ioh3420,bus=pcie.0,id=root3.0,slot=3 -device virtio-scsi-pci,id=scsi2,num_queues=4,bus=root3.0 \ -drive file=en_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10189290.iso,if=none,readonly=on,format=raw,id=cdrom1,media=cdrom -device scsi-disk,bus=scsi2.0,drive=cdrom1,id=scsi2-0 \ -device ioh3420,bus=pcie.0,id=root4.0,slot=4