Arch Linux

panaut0lordv

Member

Registered: 2016-04-18

Posts: 3

[SOLVED] 4.15+ NVMe hijacks my vfio-pci device (prevents VM start)

Hello,
I first assumed that something changed in iommu_groups as I started getting following error when starting qemu-kvm:

group 1 is not viable
Please ensure all devices within the iommu_group are bound to their vfio bus driver.

But after collecting outputs to post here I found the culprit:

Linux turtul-pc 4.14.15-1-ARCH #1 SMP PREEMPT Tue Jan 23 21:49:25 UTC 2018 x86_64 GNU/Linux
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 [144d:a802] (rev 01)
        Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 [144d:a801]
        Kernel driver in use: vfio-pci
        Kernel modules: nvme

Linux turtul-pc 4.17.0-1-ARCH #1 SMP PREEMPT Mon Jun 4 20:39:17 UTC 2018 x86_64 GNU/Linux
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 [144d:a802] (rev 01)
        Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 [144d:a801]
        Kernel driver in use: nvme

This is my modprobe.d, after making any changes I run "mkinitcpio -p linux"

cat /etc/modprobe.d/*
blacklist nouveau
blacklist radeon amdgpu
#blacklist nvme

#softdep nvme pre: vfio vfio-pci
softdep radeon pre: vfio-pci
options vfio-pci ids=8086:15a1,1002:67b0,1002:aac8,144d:a802

nvme blacklist and softdep don't make any difference but I included them to show you what I was trying to do

Any suggestions?

Best regards,
Michal

Last edited by panaut0lordv (2018-10-16 20:26:02)

panaut0lordv

Member

Registered: 2016-04-18

Posts: 3

Re: [SOLVED] 4.15+ NVMe hijacks my vfio-pci device (prevents VM start)

Solution:
As I couldn't prevent nvme bind during boot I came up with solution to rebind device later on.

# echo 0000:02:00.0 > /sys/bus/pci/devices/0000\:02\:00.0/driver/unbind 
# echo 144d a802 > /sys/bus/pci/drivers/vfio-pci/new_id