Bug 1420216
| Summary: | Migration from RHEL7.3.z -> RHEL4 failed with e1000e nic card | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | huiqingding <huding> |
| 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.4 | CC: | chayang, dgilbert, juzhang, knoel, michen, mrezanin, virt-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.8.0-5.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1420195 | Environment: | |
| Last Closed: | 2017-08-01 23:44:45 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
huiqingding
2017-02-08 08:09:07 UTC
Do vmstate check and the result is as following: # python vmstate-static-checker.py -s rhel7.3.json_7.3 -d rhel7.4.json_7.3 Section "e1000e", Description "e1000e": expected field "intr_state", got "core.rxbuf_min_shift"; skipping rest Section "rtl8139", Description "rtl8139": expected field "tally_counters", got "tally_counters.TxOk"; skipping rest OK, can reproduce this, easiest test is: /usr/libexec/qemu-kvm -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -device e1000e,multifunction=off -nographic Yes, the 'intr_state' field spotted by the checker is the problem. 7.3 (based on 2.6) backported e1000e by pulling in commits: 6f3fbe4ed06a54b14716e619f1053c073fddae49 103916cbe923f08080717942f1b5f9c4eb74aa11 that went in upstream after 2.6. However before 2.7.0's release another two commits were added to e1000e: e0af5a0e8b74c674d29be3224b7ec16ba278e99c 66bf7d58d830e6370895e4f1bb1257d135661872 which removed the need for that field. Since these went in before 2.7.0 was released there's no upstream compatibility problem since it was all new in 2.7.0. Posted downstream fix. [RHEL-7.4 qemu-kvm-rhev PATCH 1/1] migcompat/e1000e: Work around 7.3 msi/intr_state field QE: It probably needs testing on a few different OSs and machine types etc to make sure network traffic is OK after migration. Fix included in qemu-kvm-rhev-2.8.0-5.el7 Based on comment #8 and #10, set this bug to be verified and continue to track bz1447935. 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 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 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 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 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 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 |