-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unraid 6.12 RC3 #3
Comments
您好,有没有在tools->system device里面把设备绑定到vfio-pci,要去那里绑定了才能每次启动都生效。 |
那查一查日志,看看提示的vfio-bind错误是哪些设备导致的 |
Loading config from /boot/config/vfio-pci.cfg IOMMU group members (sans bridges): Binding... success... Device 8086:1528 at 0000:05:00.0 bound to vfio-pciProcessing 0000:05:00.1 8086:1528 IOMMU group members (sans bridges): Binding... success... Device 8086:1528 at 0000:05:00.1 bound to vfio-pciProcessing 0000:08:00.0 8086:125c IOMMU group members (sans bridges): Binding... success... Device 8086:125c at 0000:08:00.0 bound to vfio-pciProcessing 0000:09:00.0 8086:125c IOMMU group members (sans bridges): Binding... success... Device 8086:125c at 0000:09:00.0 bound to vfio-pciProcessing 0000:00:02.1 8086:4692Processing 0000:00:02.2 8086:4692Devices listed in /sys/bus/pci/drivers/vfio-pci: 看这个日志,好像没有啥错误 |
Issue is VFIO check is completed before plugin is loaded so 2.1 and 2.2 don't exist. You don't need to bind them to VFIO. unraid 上面的一个老哥给的反馈 |
看起来没问题,手动启动VM应该是正常的,可能是6.12.0-rc3里加载插件和启动VM的顺序变了,在加载插件之前先尝试启动VM,所以找不到绑定的设备了。我升级个rc3试一下,看看有没有办法。 |
他是Unraid认证的社区开发者,跟我想的差不多。 |
我换了个方式,虚拟出来的显卡不绑定直通,直接在VM里面用就好了。 |
对,也可以,启动虚拟机的时候会自动把直通的pci设备用vfio-pci去驱动,而虚拟的vf显卡主机用不上的,直接虚拟机里用就行。 |
哇 cool 我这两天也因此困扰,导致我openwrt 都不能在重启后自启动。都不绑定后啥问题都没了 该调用还是调用 舒服了~ |
重启之后报错
VM Autostart disabled due to vfio-bind error
The text was updated successfully, but these errors were encountered: