QuoteUpon boot, if all PCI devices specified in 'config/vfio-pci.cfg' file do not properly bind, VM Autostart is prevented. You may still start individual VMs. This is to prevent Unraid host crash if hardware PCI IDs changed because of a kernel update or physical hardware change. To restore VM autostart, examine '/var/log/vfio-pci-error' and remove offending PCI IDs from 'config/vfio-pci.cfg' file and reboot.
FROM https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6120-rc3-available-r2349/
I have a ethernet controller with SR-IOV capability. I passthrough VF to VMs to lower cpu usage.
But 6.12 makes my VMs never auto start due to vfio-bind error.
Content of /boot/config/go
#!/bin/bash # Enable SR-IOV for eth echo 1 > /sys/bus/pci/devices/0000:02:00.0/sriov_numvfs # Start the Management Utility /usr/local/sbin/emhttp &
Content of /boot/config/vfio-pci.cfg
BIND=0000:02:10.0|8086:1520
vfio-pci logs:
# cat /var/log/vfio-pci Loading config from /boot/config/vfio-pci.cfg BIND=0000:02:10.0|8086:1520 --- Processing 0000:02:10.0 8086:1520 --- Devices listed in /sys/bus/pci/drivers/vfio-pci: vfio-pci binding complete # cat /var/log/vfio-pci-errors Error: Device 0000:02:10.0 does not exist, unable to bind device
In addition, I find vfio-pci.cfg is processed in "/etc/rc.d/rc.S". Maybe I need to write value to sriov_numvfs before rc.S to make it pass the check.
I don't know where to write my scripts.
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.