Bug 1434784
Summary: | migration: 7.4->7.2 error while loading state for instance 0x0 of device 'apic' | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Dr. David Alan Gilbert <dgilbert> |
Component: | qemu-kvm-rhev | Assignee: | Dr. David Alan Gilbert <dgilbert> |
Status: | CLOSED ERRATA | QA Contact: | huiqingding <huding> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.4 | CC: | chayang, huding, juzhang, michen, mrezanin, pbonzini, qzhang, virt-maint, xianwang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-02 03:39:56 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
Dr. David Alan Gilbert
2017-03-22 11:33:59 UTC
Caused by new apic subsection apic_irq_delivered in 2.9, added by : v2.8.0-850-g07bfa35 apic: save apic_delivered flag Paolo is reverting that upstream. This issue is hit when do migration from rhel7.4 to rhel7.3.z on x86_64. The reproduction is as following: version: RHEL7.4 (src host) 3.10.0-623.el7.x86_64 qemu-kvm-rhev-2.9.0-0.el7.mrezanin201703210848.x86_64 RHEL7.3.z(dst host) 3.10.0-514.17.1.el7.x86_64 qemu-kvm-rhev-2.6.0-28.el7_3.7.x86_64 steps: 1)Boot a guest in rhel7.4 host: # /usr/libexec/qemu-kvm -machine pc-i440fx-rhel7.3.0 -monitor stdio 2)Boot a guest in rhel7.3.z host with incoming # /usr/libexec/qemu-kvm -machine pc-i440fx-rhel7.3.0 -monitor stdio -incoming tcp:0:5801 3)in rhel7.4 host, do migration (qemu) migrate -d tcp:10.66.10.208:5801 Actual result: migration failed, check the status of migration: on rhel7.4(src host) (qemu) info status VM status: running (qemu) info migrate Migration status: failed on rhel7.3.z(dst host) (qemu) qemu-kvm: error while loading state for instance 0x0 of device 'apic' qemu-kvm: load of migration failed: No such file or directory How reproducible: 3/3 This should be fixed by 5354edd286ea6e956b81da66c9dcc5e47028198e upstream which is Paolo's revert. Reproduce this bug: 7.2.z: kernel-3.10.0-327.53.1.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.25.x86_64 7.4: kernel-3.10.0-650.el7.x86_64 qemu-kvm-rhev-2.9.0-0.el7.mrezanin201703210848.x86_64 Reproduce steps: 1. boot a guest in 7.4 host: # /usr/libexec/qemu-kvm -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off,vmport=off -cpu IvyBridge -m 4096 -no-hpet -drive file=/mnt/stable_guest_abi/rhel74-64-virtio.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -net none -monitor stdio 2. boot the guest in 7.2.z host: # /usr/libexec/qemu-kvm -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off,vmport=off -cpu IvyBridge -m 4096 -no-hpet -drive file=/mnt/stable_guest_abi/rhel74-64-virtio.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -chardev stdio,mux=on,id=mon -net none -monitor stdio -incoming tcp:0:5800 3. do migration (qemu) migrate -d tcp:10.73.196.143:5800 Result: Migration is failed and dst qemu quits with: qemu-kvm: error while loading state for instance 0x0 of device 'apic' qemu-kvm: load of migration failed: No such file or directory Verify this bug: 7.2.z: kernel-3.10.0-327.53.1.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.25.x86_64 7.4: kernel-3.10.0-650.el7.x86_64 qemu-kvm-rhev-2.9.0-1.el7.x86_64 Test using the above command line and migration can be finished normally. Also test 7.4->7.3.z, the result is pass. Based on comment #5, set this bug to be 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 |