1440619 – Reboot guest will induce error message - KVM: Failed to create TCE table for liobn 0x80000001

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1440619 - Reboot guest will induce error message - KVM: Failed to create TCE table for liobn 0x80000001

Summary: Reboot guest will induce error message - KVM: Failed to create TCE table for ...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	qemu-kvm-rhev
Sub Component:
Version:	7.4
Hardware:	ppc64le
OS:	Unspecified
Priority:	medium
Severity:	low
Target Milestone:	rc
Target Release:	---
Assignee:	David Gibson
QA Contact:	Min Deng
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2017-04-10 06:16 UTC by Min Deng
Modified:	2017-08-02 04:35 UTC (History)
CC List:	8 users (show)
Fixed In Version:	qemu-kvm-rhev-2.9.0-2.el7
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2017-08-02 04:35:59 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
x86screenshot (25.03 KB, image/png) 2017-04-10 10:03 UTC, Min Deng	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:2392	0	normal	SHIPPED_LIVE	Important: qemu-kvm-rhev security, bug fix, and enhancement update	2017-08-01 20:04:36 UTC

Description Min Deng 2017-04-10 06:16:34 UTC

Description of problem:
Reboot guest will induce an error message - KVM: Failed to create TCE table for liobn 0x80000001

Version-Release number of selected component (if applicable):
kernel-3.10.0-645.el7.ppc64le (hostandguest)
qemu-kvm-rhev-2.9.0-0.el7.patchwork201703291116.ppc64le
SLOF-20170303-1.git66d250e.el7.noarch
How reproducible:
4/4

Steps to Reproduce:
1.boot up guest with the following cli,
  /usr/libexec/qemu-kvm -name virt-tests-vm1 -sandbox off -machine pseries-rhel7.4.0 -nodefaults -vga std -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=03,disable-legacy=off,disable-modern=off -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=qcow2,file=rhel74-ppc64le-virtio-scsi.qcow2 -device scsi-hd,id=image1,drive=drive_image1 -numa node -qmp tcp:0:4444,server,nowait -vnc :1 -rtc base=utc,clock=host,driftfix=slew -boot order=cdn,once=c,menu=off,strict=off -enable-kvm -monitor stdio -device nec-usb-xhci,id=usb1 -device usb-kbd,id=input0 -device usb-mouse,id=input1 -device usb-tablet,id=input2 -netdev tap,script=/etc/qemu-ifup,downscript=/etc/qemu-down,id=hostnet1,vhost=on -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:11:36:3f:01
2.Within guest 
  reboot
  From monitor
  system_reset
3.

Actual results:
There is an error from monitor
(qemu) ststem_restKVM: Failed to create TCE table for liobn 0x80000001

Expected results:
There is no any issues

Additional info:

Comment 2 Min Deng 2017-04-10 06:18:43 UTC

QE will have a try on x86 platform the relevant result will be updated to the bug as soon as possible.

Comment 3 Min Deng 2017-04-10 10:02:23 UTC

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.

Comment 4 Min Deng 2017-04-10 10:03:12 UTC

Created attachment 1270436 [details]
x86screenshot

Comment 6 Eduardo Habkost 2017-04-10 14:32:10 UTC

(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.

Comment 7 Min Deng 2017-04-11 02:53:25 UTC

(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"

Comment 8 David Gibson 2017-04-13 05:54:24 UTC

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.

Comment 11 Miroslav Rezanina 2017-04-28 10:07:56 UTC

Fix included in qemu-kvm-rhev-2.9.0-2.el7

Comment 13 Min Deng 2017-05-04 05:27:32 UTC

(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.

Comment 14 Min Deng 2017-05-04 09:33:14 UTC

According to comment 13 QE move it to status verified.

Comment 16 errata-xmlrpc 2017-08-02 04:35:59 UTC

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

Note You need to log in before you can comment on or make changes to this bug.