Bug 1369641
Summary: | Boot guest with 'kernel-irqchip=split', 'intremap=true' and e1000, guest fails to get ip and call trace occurs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Pei Zhang <pezhang> |
Component: | qemu-kvm-rhev | Assignee: | Peter Xu <peterx> |
Status: | CLOSED ERRATA | QA Contact: | Pei Zhang <pezhang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | chayang, hhuang, ilmostro7, imammedo, juzhang, knoel, michen, mrezanin, peterx, virt-maint, xfu, xiywang |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.8.0-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 23:34:44 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
Pei Zhang
2016-08-24 05:10:40 UTC
As Peter suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1358653#c6, add '-global ioapic.version=0x20', then the network becomes well. So this bug may not a bug. (In reply to Pei Zhang from comment #2) > As Peter suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1358653#c6, > > add '-global ioapic.version=0x20', then the network becomes well. So this > bug may not a bug. Pei, I think so. Shall we change it to NOTABUG? (In reply to Peter Xu from comment #3) > (In reply to Pei Zhang from comment #2) > > As Peter suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1358653#c6, > > > > add '-global ioapic.version=0x20', then the network becomes well. So this > > bug may not a bug. > > Pei, > > I think so. Shall we change it to NOTABUG? OK. Close this bug as 'NOTABUG' as Comment 2 and Comment 3. *** Bug 1378140 has been marked as a duplicate of this bug. *** Peter, Shall we reopen this bug and fix it upstream as well? I think that emulated HW should work by default without need to specify some obscure parameter on CLI or if it's not possible to fix then at least QEMU should warn user that device won't be usable in specified configuration. Hi, Igor, (In reply to Igor Mammedov from comment #6) > Peter, > > Shall we reopen this bug and fix it upstream as well? > > I think that emulated HW should work by default without need to specify some > obscure parameter on CLI or if it's not possible to fix then at least QEMU > should warn user that device won't be usable in specified configuration. The problem is: it only happens on some kernels, and we could never know what kernel the guest is running. (and actually this is possibly a upstream kernel bug on IR, which is on my todo list. this is another story.) But I agree with you that this is awkward. The best solution is to let it run by default. Since now we have released QEMU 2.7, maybe it's time to post a patch for QEMU 2.8 upstream (and for rhev 7.4 as well). If you think this is the right way to go, please just OPEN it and I'll handle the rest. Thanks. I believe this just occurred on my RHEL7.3 system and a fedora25 guest; though, there is no current RHEV subscription on the system. It might be related to the network adapter having been used in Passthrough mode. Verification: Versions: 3.10.0-663.rt56.582.el7.x86_64/3.10.0-663.el7.x86_64 qemu-kvm-rhev-2.9.0-3.el7.x86_64 Steps: Same with Description. - The e1000 network device can get IP. - No call trace info shows in host. - No other errors with reboot/shutdown VM. So this bug has been fixed well. Moving 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 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 |