Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This is something that has been observed when upgrading from a RHEL 7 (dracut-033-572.el7.x86_64) to a RHEL 8 (dracut-049-70.git20200228.el8.x86_64) in a RHOSP upgrade using LEAPP.
So far, some RHOSP installations were creating a /etc/modules-load.d/vfio-pci.conf file.
Its content:
"""
# This file is managed by the puppet kmod module.
vfio-pci
"""
On RHEL 7, the vfio-pci dependencies are as follows:
# modprobe --ignore-install --show-depends vfio-pci |sort -u
insmod /lib/modules/3.10.0-1160.el7.x86_64/kernel/drivers/vfio/pci/vfio-pci.ko.xz
insmod /lib/modules/3.10.0-1160.el7.x86_64/kernel/drivers/vfio/vfio_iommu_type1.ko.xz
insmod /lib/modules/3.10.0-1160.el7.x86_64/kernel/drivers/vfio/vfio.ko.xz
insmod /lib/modules/3.10.0-1160.el7.x86_64/kernel/virt/lib/irqbypass.ko.xz
And the initramfs contains them all:
# dracut -f /boot/initramfs-$(uname -r).img
# lsinitrd /boot/initramfs-$(uname -r).img |grep -E '(vfio|irqby).*ko'
-rw-r--r-- 1 root root 24504 Aug 18 15:15 usr/lib/modules/3.10.0-1160.el7.x86_64/kernel/drivers/vfio/pci/vfio-pci.ko.xz
-rw-r--r-- 1 root root 10104 Aug 18 15:15 usr/lib/modules/3.10.0-1160.el7.x86_64/kernel/drivers/vfio/vfio_iommu_type1.ko.xz
-rw-r--r-- 1 root root 13956 Aug 18 15:15 usr/lib/modules/3.10.0-1160.el7.x86_64/kernel/drivers/vfio/vfio.ko.xz
-rw-r--r-- 1 root root 2640 Aug 18 15:15 usr/lib/modules/3.10.0-1160.el7.x86_64/kernel/virt/lib/irqbypass.ko.xz
On RHEL8,
# modprobe --ignore-install --show-depends vfio-pci |sort -u
insmod /lib/modules/4.18.0-193.el8.x86_64/kernel/drivers/vfio/pci/vfio-pci.ko.xz
insmod /lib/modules/4.18.0-193.el8.x86_64/kernel/drivers/vfio/vfio_iommu_type1.ko.xz
insmod /lib/modules/4.18.0-193.el8.x86_64/kernel/drivers/vfio/vfio.ko.xz
insmod /lib/modules/4.18.0-193.el8.x86_64/kernel/drivers/vfio/vfio_virqfd.ko.xz
insmod /lib/modules/4.18.0-193.el8.x86_64/kernel/virt/lib/irqbypass.ko.xz
But the initramfs lacks the vfio_iommu_type1.
# lsinitrd /boot/initramfs-$(uname -r).img |grep -E '(vfio|irqby).*ko'
-rw-r--r-- 1 root root 24796 Feb 28 2020 usr/lib/modules/4.18.0-193.el8.x86_64/kernel/drivers/vfio/pci/vfio-pci.ko.xz
-rw-r--r-- 1 root root 14144 Feb 28 2020 usr/lib/modules/4.18.0-193.el8.x86_64/kernel/drivers/vfio/vfio.ko.xz
-rw-r--r-- 1 root root 3444 Feb 28 2020 usr/lib/modules/4.18.0-193.el8.x86_64/kernel/drivers/vfio/vfio_virqfd.ko.xz
-rw-r--r-- 1 root root 3040 Feb 28 2020 usr/lib/modules/4.18.0-193.el8.x86_64/kernel/virt/lib/irqbypass.ko.xz
This is a problem as the vfio-pci / vfio modules get loaded, but the iommu_type1 does not.
Later tools and ovs/dpdk won't reload vfio kmods.
To be fair, my current recommendation to the RHOSP guys is to remove the vfio-pci.conf file.
We don't need vfio in the initramfs and we can rely on driverctl (a tool that binds devices for dpdk) for vfio-pci loading.
But I still opened this bz as I think this is a regression from RHEL 7 to RHEL 8.
Comment 1Sergii Golovatiuk
2020-11-18 20:40:17 UTC
*** Bug 1889675 has been marked as a duplicate of this bug. ***