Bug 1449490
Summary: | [q35] guest hang after do migration with virtio-scsi-pci. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | xiagao |
Component: | qemu-kvm-rhev | Assignee: | Sameeh Jubran <sjubran> |
Status: | CLOSED ERRATA | QA Contact: | jingzhao <jinzhao> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.4 | CC: | ailan, chayang, dgilbert, drjones, hhuang, huding, jinzhao, juzhang, knoel, lijin, michen, mrezanin, phou, qzhang, virt-bugs, virt-maint, wyu, xiagao, yvugenfi |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.9.0-7.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-02 04:38:29 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: | |||
Bug Blocks: | 1376765 |
Description
xiagao
2017-05-10 06:47:34 UTC
Hit the same issue on q35+seabios. 1) Can you try with a different NIC than e1000e - I'm tracking a separate e1000e migration bug 2) Does a Linux guest fail in the same way? (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. (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. 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. A patch that fixes the bug for e1000e device was sent to upstream Qemu: http://lists.nongnu.org/archive/html/qemu-devel/2017-05/msg04019.html *** Bug 1447935 has been marked as a duplicate of this bug. *** Fix included in qemu-kvm-rhev-2.9.0-7.el7 Reproduce the issue on qemu-kvm-rhev-2.9.0-3.el7.x86_64 and verified the issue on qemu-kvm-rhev-2.9.0-7.el7.x86_64 ps: qemu command line /usr/libexec/qemu-kvm \ -machine q35,smm=on,accel=kvm \ -cpu Opteron_G3 \ -nodefaults -rtc base=utc \ -m 2G \ -smp 2,sockets=2,cores=1,threads=1 \ -enable-kvm \ -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \ -k en-us \ -nodefaults \ -drive file=/usr/share/OVMF/OVMF_CODE.secboot.fd,if=pflash,format=raw,unit=0,readonly=on \ -drive file=/home/OVMF_VARS.fd,if=pflash,format=raw,unit=1 \ -serial unix:/tmp/serial0,server,nowait \ -debugcon file:/home/ovmf.log \ -global isa-debugcon.iobase=0x402 \ -boot menu=on \ -qmp tcp:0:6666,server,nowait \ -vga qxl \ -device pcie-root-port,bus=pcie.0,id=root3 \ -device virtio-scsi-pci,id=scsi1,bus=root3 \ -drive file=win10-ovmf-bk.qcow2,if=none,id=drive-scsi-disk0,format=qcow2,cache=none,werror=stop,rerror=stop -device scsi-hd,drive=drive-scsi-disk0,id=scsi-disk0,bus=scsi1.0 \ -device pcie-root-port,bus=pcie.0,id=root0,multifunction=on,chassis=1,addr=0xa.0 \ -device e1000e,netdev=tap10,mac=9a:6a:6b:6c:6d:6e,bus=root0 -netdev tap,id=tap10 \ -device pcie-root-port,bus=pcie.0,id=root1,chassis=11,addr=0xa.1 \ -device pcie-root-port,bus=pcie.0,id=root2,chassis=12,addr=0xa.2 \ -device pcie-root-port,bus=pcie.0,id=root8,slot=3 \ -cdrom /home/en_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10189290.iso \ -device ahci,id=ahci0 \ -drive file=/usr/share/virtio-win/virtio-win-1.9.0.iso,if=none,id=drive-scsi-disk1,format=raw,cache=none,werror=stop,rerror=stop -device ide-cd,drive=drive-scsi-disk1,id=scsi-disk1,bus=ahci0.0 \ -monitor stdio \ -vnc :2 \ According to comment 18, changed the status to verified 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 |