-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by joykingdom
-
-
9 minutes ago, SimonF said:
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.
For now suggest remove bindings from system devices.
Before 6.12 RC3 is ok
So I can not use IGPU SR-IOV again?
-
-
1 hour ago, SimonF said:
You need to look at the VFIO log to see which devices didn't bind. This is to safe guard against hardware changes that may crash host if VM starts without correct hardware passthru.
VFIO log
Loading config from /boot/config/vfio-pci.cfg
BIND=0000:05:00.0|8086:1528 0000:05:00.1|8086:1528 0000:08:00.0|8086:125c 0000:09:00.0|8086:125c 0000:00:02.1|8086:4692 0000:00:02.2|8086:4692---
Processing 0000:05:00.0 8086:1528
Vendor:Device 8086:1528 found at 0000:05:00.0IOMMU group members (sans bridges):
/sys/bus/pci/devices/0000:05:00.0/iommu_group/devices/0000:05:00.0Binding...
success...
Device 8086:1528 at 0000:05:00.0 bound to vfio-pci
---
Processing 0000:05:00.1 8086:1528
Vendor:Device 8086:1528 found at 0000:05:00.1IOMMU group members (sans bridges):
/sys/bus/pci/devices/0000:05:00.1/iommu_group/devices/0000:05:00.1Binding...
success...
Device 8086:1528 at 0000:05:00.1 bound to vfio-pci
---
Processing 0000:08:00.0 8086:125c
Vendor:Device 8086:125c found at 0000:08:00.0IOMMU group members (sans bridges):
/sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.0Binding...
success...
Device 8086:125c at 0000:08:00.0 bound to vfio-pci
---
Processing 0000:09:00.0 8086:125c
Vendor:Device 8086:125c found at 0000:09:00.0IOMMU group members (sans bridges):
/sys/bus/pci/devices/0000:09:00.0/iommu_group/devices/0000:09:00.0Binding...
success...
Device 8086:125c at 0000:09:00.0 bound to vfio-pci
---
Processing 0000:00:02.1 8086:4692
---
Processing 0000:00:02.2 8086:4692
---
Devices listed in /sys/bus/pci/drivers/vfio-pci:
lrwxrwxrwx 1 root root 0 Apr 22 09:29 0000:05:00.0 -> ../../../../devices/pci0000:00/0000:00:1c.4/0000:05:00.0
lrwxrwxrwx 1 root root 0 Apr 22 09:29 0000:05:00.1 -> ../../../../devices/pci0000:00/0000:00:1c.4/0000:05:00.1
lrwxrwxrwx 1 root root 0 Apr 22 09:29 0000:08:00.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/0000:06:00.0/0000:07:03.0/0000:08:00.0
lrwxrwxrwx 1 root root 0 Apr 22 09:29 0000:09:00.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/0000:06:00.0/0000:07:07.0/0000:09:00.0
vfio-pci binding complete -
6.12 RC3
After reboot
VM Autostart disabled due to vfio-bind error
-
On 4/5/2023 at 4:10 PM, ich777 said:
Are you on the latest BIOS? Can you maybe contact the manufacturer about that, this is something that I can't fix. As said above this is most certainly a bug in your BIOS.
In which PCIe slot do you have the card installed?
Have you yet tried to boot into Legacy Mode?
EDIT: Wait, now that I see it, this is a mobile T400 chip, what card is this exactly.
I'm not 100% sure if the default Nvidia driver supports mobile chips and even if it does it seems that you need a modified driver for this card because Nvidia is most certainly not selling PCIe GPUs with mobile chips.
Except for the persistent error log, the nvidia T400 driver installed with this plugin works fine, in Emby or plex.
-
13 hours ago, ich777 said:
This is most certainly caused by a bug in your BIOS, have you yet checked if you are on the latest BIOS version?
Why do you have created the nvidia.conf file in your modprobe.d folder:
options nvidia NVreg_OpenRmEnableUnsupportedGpus=1
you even don't run the open source driver.
Try to boot with CSM (Legacy Mode) and see if that solves the issue but most certainly this is a bug in your BIOS.
Also make sure that you've enabled Above 4G Decoding and Resizable BAR Support in your BIOS.
I deleted the nvidia.conf;
Enabled Above 4G Decoding and Resizable BAR Support in your BIOS still can not solove
Boot with CSM,unraid cannot boot.
The error logs increase fast, any thing I can do?
-
-
-
3 hours ago, JorgeB said:
After the log rotates it should be fine to delete /var/log/syslog1 and/or /var/log/syslog2, but ti's something I've never tried.
I disable the nvidia T400, the error log was gone
-
On 4/2/2023 at 7:18 PM, JorgeB said:
Then probably not much else you can do, a different kernel could help, did you try v6.11.5?
Besides restarting, is there any other way to quickly delete these logs?
-
6.11.5 and 6.12 are the same.
-
The bios version is up to date
-
-
7 minutes ago, JorgeB said:
Did you try a different browser? Like mentioned array appeared to have started correctly.
I can access unraid from brower, but the monitor stuck at starting samba both normal and safe mode.
-
29 minutes ago, JorgeB said:
Server appears to have started correctly, try closing and re-opening the browser, if the same reboot in safe mode.
the same reboot in safe mode. still STUCK AT STARTING SAMBA
-
-
1 hour ago, JorgeB said:
Several crashes, start by running memtest, first crash mentions cifs, so could also be SMB related:
Jul 13 09:06:59 MyUnraid kernel: cifs_filldir.constprop.0+0x3ac/0x4fd [cifs] Jul 13 09:06:59 MyUnraid kernel: cifs_readdir+0x5c7/0x639 [cifs]
What need I do ?
-
-
6 hours ago, JorgeB said:
Enable the syslog server and post that and the complete diagnostics after a crash.
-
-
有没有大哥成功的?实在找不到资料
-
On 7/2/2022 at 1:06 PM, jinlife said:
Hello Acidcliff, I built a kernel with the IOV code in intel LTS Kernel 5.15. It looks fine to run but I have no 12th CPU to test the i915 SR-IOV ability.
Would you please try it? It was built for unraid 6.10.3, please just overwrite these files to the flash drive.
Please backup original 4 files, copying them back will revert the change.
https://drive.google.com/drive/folders/1bAnedRHWaz7QGQAkO7xWohhnjDxSfbqS?usp=sharing
It is just experiment, may not work. Maybe the code is not the only condition.
Anyone has tried ?
VM Backup Plugin
in User Customizations
Posted
This plugin has problems with 6.12rc3