Bug 1440619
| Summary: | Reboot guest will induce error message - KVM: Failed to create TCE table for liobn 0x80000001 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Min Deng <mdeng> | ||||
| Component: | qemu-kvm-rhev | Assignee: | David Gibson <dgibson> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Min Deng <mdeng> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.4 | CC: | dgibson, ehabkost, knoel, michen, mrezanin, qzhang, thuth, virt-maint | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | ppc64le | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | qemu-kvm-rhev-2.9.0-2.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-08-02 04:35:59 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: | |||||||
| Attachments: |
|
||||||
|
Description
Min Deng
2017-04-10 06:16:34 UTC
QE will have a try on x86 platform the relevant result will be updated to the bug as soon as possible. Additional analysis for the bug.
PPC
If add "-m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2" to the original's cli,the bug won't be reproduced on ppc64le.
X86
Besides,if without "-m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2" the guest *cannot* boot up successfully at all,please have a look on the screen shot.
From QE's opinions, we could not simply tell if it was reproducible or not for x86 since the different phenomenon disturbed the result.
if with "-m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2" the bug can not be reproduced on x86 either.
Created attachment 1270436 [details]
x86screenshot
(In reply to Min Deng from comment #3) > Additional analysis for the bug. > PPC > If add "-m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2" to the > original's cli,the bug won't be reproduced on ppc64le. We have two variables here: the CPU topology and RAM size. Please test them separately to confirm which one makes the bug reproducible. > > X86 > Besides,if without "-m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2" > the guest *cannot* boot up successfully at all,please have a look on the > screen shot. That's probably because the default RAM size on x86 is too small for most guest OSes (128MB). > From QE's opinions, we could not simply tell if it was reproducible or not > for x86 since the different phenomenon disturbed the result. > if with "-m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2" the > bug can not be reproduced on x86 either. "Failed to create TCE table for liobn" is an error message from ppc-specific code, so this bug is ppc-specific. (In reply to Eduardo Habkost from comment #6) > (In reply to Min Deng from comment #3) > > Additional analysis for the bug. > > PPC > > If add "-m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2" to the > > original's cli,the bug won't be reproduced on ppc64le. > > We have two variables here: the CPU topology and RAM size. Please test them > separately to confirm which one makes the bug reproducible. Thanks for the comments and it is steadily reproduced while cli without "-m 4096" I've had a look at the code around this, and I'm pretty sure the bug is cosmetic only. This basically means that we couldn't enable the KVM acceleration for updates to the guest's IOMMU tables. From the LIOBN quoted I can tell it's on the second window of the primary PCI bus. The second window is the optional 64-bit window which can be configured by the guest. The current KVM acceleration for IOMMU updates only supports 32-bit IOMMU windows, hence the error. qemu will fall back to managing IOMMU updates itself, which should work fine. Hence cosmetic only. Lowering severity accordingly. In fact I already have stage an upstream patch which will remove this error message (and also use the acceleration for 64-bit windows which has been added in more recent kernels). I expect to push this soon after the 2.10 window opens. Fix included in qemu-kvm-rhev-2.9.0-2.el7 (In reply to Miroslav Rezanina from comment #11) > Fix included in qemu-kvm-rhev-2.9.0-2.el7 The bug can be reproduced on old builds kernel-3.10.0-645.el7.ppc64le (hostandguest) qemu-kvm-rhev-2.9.0-0.el7.patchwork201703291116.ppc64le Verified the bug on the new builds kernel-3.10.0-657.el7.ppc64le qemu-kvm-rhev-2.9.0-2.el7.ppc64le Steps please refer to comment 0 Actual results: There is no any errors Expected results: There is no any errors Draw a conclusion,the bug has been fixed,thanks a lot. According to comment 13 QE move it to status 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 |