Bug 1392876
| Summary: | windows guests migration from rhel6.8-z to rhel7.3 with virtio-net-pci fail | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | qemu-kvm-rhev | Assignee: | Dr. David Alan Gilbert <dgilbert> |
| Status: | CLOSED ERRATA | QA Contact: | huiqingding <huding> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.3 | CC: | chayang, dgilbert, hhuang, huding, jen, jherrman, jsuchane, juzhang, knoel, lijin, lprosek, michal.skrivanek, mrezanin, mst, pbonzini, phou, sherold, snagar, virt-bugs, virt-maint, wyu, ykaul, ymankad, yvugenfi |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.6.0-28.el7_3.1 | Doc Type: | Bug Fix |
| Doc Text: |
Attempting to migrate a Windows guest virtual machine that was using the virtio-net-pci device from a Red Hat Enterprise Linux (RHEL) 6 host to a RHEL 7.3 host previously caused the guest to terminate unexpectedly, because the ctrl_guest_offloads feature was disabled on the destination host. This update enables ctrl_guest_offloads on the destination host, and the described migration works as expected.
|
Story Points: | --- |
| Clone Of: | 1378334 | Environment: | |
| Last Closed: | 2017-01-17 20:09:41 UTC | Type: | --- |
| 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: | 1378334 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-11-08 12:11:24 UTC
Fix included in qemu-kvm-rhev-2.6.0-28.el7_3.1 Reproduce this bug using the following version: Source RHEL6.8.z host: kernel-2.6.32-642.13.1.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.491.el6_8.3.x86_64 Destination RHEL7.3 host: kernel-3.10.0-514.6.1.el7.x86_64 qemu-kvm-rhev-2.6.0-28.el7.x86_64 Reproduce steps: 1. boot a win10-64 guest in source host: # /usr/libexec/qemu-kvm \ -enable-kvm \ -m 2G \ -smp 2 \ -M rhel6.6.0 \ -nodefconfig \ -nodefaults \ -cpu SandyBridge \ -rtc base=localtime,driftfix=slew \ -boot order=cd,menu=on \ -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ -drive file=en_windows_10_enterprise_x64_dvd_6851151.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw \ -device ide-drive,drive=drive-ide0-1-0,id=ide0-1-0,bus=ide.0,unit=1 \ -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 \ -device usb-tablet,id=input0 \ -cdrom /usr/share/virtio-win/virtio-win-1.9.0.iso \ -monitor stdio \ -qmp tcp:0:4444,server,nowait \ -vnc 0.0.0.0:0 \ -vga cirrus \ -drive file=win10.raw,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none \ -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0 \ -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0,vhost=on \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:52:4c:23:4d:90 2. install virtio-net-pci driver (virtio-win-1.9.0-3) inside guest 3. boot the guest in destination host with "-incoming tcp:0:5800" 4. do migration (qemu) migration -d tcp:10.73.196.161:5800 Actual results: after step4, migration is failed and the destination qemu-kvm quits with (qemu) qemu-kvm: Features 0x301f99a7 unsupported. Allowed features: 0x719fffe3 qemu-kvm: error while loading state for instance 0x0 of device '0000:00:04.0/virtio-net' copying E and F segments from pc.bios to pc.ram copying C and D segments from pc.rom to pc.ram qemu-kvm: load of migration failed: Operation not permitted Verify this bug using the following version: Source RHEL6.8.z host: kernel-2.6.32-642.13.1.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.491.el6_8.3.x86_64 Destination RHEL7.3 host: kernel-3.10.0-514.6.1.el7.x86_64 qemu-kvm-rhev-2.6.0-28.el7_3.2.x86_64 Test the same steps as comment #6, the result is that migration can be finished normally. Based on comment #7, 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://rhn.redhat.com/errata/RHBA-2017-0115.html |