On Mon, 1 Jun 2020 at 14:38, Roger Lawhorn <r...@twc.com> wrote: > > ok. > > $ grep VFIO config-5.4.43-050443-generic > CONFIG_KVM_VFIO=y > CONFIG_VFIO_IOMMU_TYPE1=y > CONFIG_VFIO_VIRQFD=y > CONFIG_VFIO=y > CONFIG_VFIO_NOIOMMU=y > CONFIG_VFIO_PCI=y > CONFIG_VFIO_PCI_VGA=y > CONFIG_VFIO_PCI_MMAP=y > CONFIG_VFIO_PCI_INTX=y > CONFIG_VFIO_PCI_IGD=y > CONFIG_VFIO_MDEV=m > CONFIG_VFIO_MDEV_DEVICE=m > # CONFIG_SAMPLE_VFIO_MDEV_MTTY is not set > # CONFIG_SAMPLE_VFIO_MDEV_MDPY is not set > # CONFIG_SAMPLE_VFIO_MDEV_MDPY_FB is not set > # CONFIG_SAMPLE_VFIO_MDEV_MBOCHS is not set > > > > so if it's built in, then why does it not load? > I am thinking that they changed how you define vfio-pci options in some way. > I define them in a config file in /etc/modprobe.d/ and then rebuild all > ramdisks. >
You need to build it as a module and not built in. With it built in, the options need to be on the kernel boot line, and not in the modprobe.d config files. _______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
