Bug 1741059
Summary: | Migrate a vm from ALT-7.6 to RHELAV-8.1.0, after migration completed, vm hang and failed to reboot vm | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | xianwang <xianwang> |
Component: | qemu-kvm | Assignee: | Laurent Vivier <lvivier> |
Status: | CLOSED ERRATA | QA Contact: | Gu Nini <ngu> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 8.1 | CC: | ailan, ddepaula, dgibson, dgilbert, hhuang, juzhang, lvivier, mdeng, micai, mrezanin, ngu, qzhang, virt-maint |
Target Milestone: | rc | Keywords: | Regression, Reopened |
Target Release: | 8.1 | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93.ppc64le | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-06 07:18: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: |
Description
xianwang
2019-08-14 07:48:13 UTC
I. This issue is only hit on fast train(destination) not on slow train, i.e, if destination host with "qemu-kvm-2.12.0-83.module+el8.1.0+3852+0ba8aef0.ppc64le", I can't hit this issue with the same steps and other build information is same with bug report. II. I also could hit this issue with the following simple qemu cli: /usr/libexec/qemu-kvm \ -nodefaults \ -machine pseries-rhel7.6.0 \ -monitor stdio \ -device virtio-net-pci,mac=9a:7b:7c:7d:7e:72,id=id9HRc5V,vectors=4,netdev=idjlQN53,bus=pci.0,addr=0xa \ -netdev tap,id=idjlQN53,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \ -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x7 \ -drive file=/home/xianwang/ALT-Server-7.6-ppc64le-virtio-scsi.qcow2,format=qcow2,if=none,cache=none,id=drive_scsi1,werror=stop,rerror=stop \ -device scsi-hd,drive=drive_scsi1,id=scsi-disk1,bus=scsi1.0,channel=0,scsi-id=0x6,lun=0x3,bootindex=0 \ after migration completed on source, guest status is: (qemu) info status VM status: paused (io-error) But the following qemu cli works well: /usr/libexec/qemu-kvm \ -nodefaults \ -machine pseries-rhel7.6.0 \ -monitor stdio -incoming tcp:0:5801 \ -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x7 \ -drive file=/home/xianwang/ALT-Server-7.6-ppc64le-virtio-scsi.qcow2,format=qcow2,if=none,cache=none,id=drive_scsi1,werror=stop,rerror=stop \ -device scsi-hd,drive=drive_scsi1,id=scsi-disk1,bus=scsi1.0,channel=0,scsi-id=0x6,lun=0x3,bootindex=0 III. I have tried remove "-netdev tap,.." and "-device virtio-net-pci,.." from the qemu cli of bug report, then this issue does not exist, so, I wonder maybe this issue is related something wrong with virtio-net device. ALT-7.6 is not supported on x86_64, so, I think we could see this issue is powerpc only. I have tried several times testing this scenario on qemu3.1, but can't reproduce it, so it is a regression, the detail build information is as following: src host: 4.14.0-115.11.1.el7a.ppc64le qemu-kvm-rhev-2.12.0-18.el7_6.7.ppc64le SLOF-20171214-2.gitfa98132.el7.noarch dst host: 4.18.0-80.10.1.el8_0.ppc64le qemu-kvm-3.1.0-30.module+el8.0.1+3755+6782b0ed.ppc64le SLOF-20180702-4.git9b7ab2f.module+el8.0.1+3755+6782b0ed.noarch Guest: 4.14.0-115.11.1.el7a.ppc64le Xianwang, could you retest with qemu-kvm-4.1.0? Thanks (In reply to Laurent Vivier from comment #7) > Xianwang, > > could you retest with qemu-kvm-4.1.0? > > Thanks Yes, I think it is fixed with qemu4.1, I have tried several times on qemu4.1 and have not hit it. source: 4.14.0-115.12.1.el7a.ppc64le qemu-kvm-rhev-2.12.0-18.el7_6.7.ppc64le # cat /sys/kernel/mm/transparent_hugepage/enabled always madvise [never] destination: 4.18.0-134.el8.ppc64le qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93.ppc64le # cat /sys/kernel/mm/transparent_hugepage/enabled always [madvise] never According to comment 8, I close this BZ as fixed in CURRENTRELEASE (qemu-4.1) Based on this, I'm setting status to VERIFIED. Hi Danilo, Can you help add this bug to Advanced-Virt-RHEL-8.1.0 errata? Thanks, Qunfang Should be there. 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:3723 |