Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

After installing new nic I have problems with my vfio and my immou on version 6.12.8

Featured Replies

So Everything was working dandy until i installed a new nic for my VM 

 

Since then I coudlnt even log into my Unraid server so i pretty much wiped the whole thing clean in my flash and installed unraid lord and behold all my old configs are there. 

 

So after creating new usb to start from scratch as soon as i put my basic key all my stuff reappears which is great if it made my vfio work but it doesnt 

 

So I am trying to passthrough a couple nics to my VM but i get an error with no pci available.

 

One thing I see in my immou my dual 540 card is seperated which is weird it never did that before take a look at the pic below:

 

image.thumb.png.aa942612bb52169b7150f6915bda0bde.png

 

that never happened before and when i go use vfio-pci-ids:8086:1528 to pass through it doesnt same with my other nics it still says no available pci.

 

I have tried using downstream, multi, and both and i cannot pass anything through nothing.

 

i dont even have a vfio.cfg file anymore.

 

Please PLEASE HELP

Solved by kilasin

  • Community Expert
6 hours ago, kilasin said:

So Everything was working dandy until i installed a new nic for my VM 

 

Since then I coudlnt even log into my Unraid server so i pretty much wiped the whole thing clean in my flash and installed unraid lord and behold all my old configs are there. 

 

So after creating new usb to start from scratch as soon as i put my basic key all my stuff reappears which is great if it made my vfio work but it doesnt 

 

So I am trying to passthrough a couple nics to my VM but i get an error with no pci available.

 

One thing I see in my immou my dual 540 card is seperated which is weird it never did that before take a look at the pic below:

 

image.thumb.png.aa942612bb52169b7150f6915bda0bde.png

 

that never happened before and when i go use vfio-pci-ids:8086:1528 to pass through it doesnt same with my other nics it still says no available pci.

 

I have tried using downstream, multi, and both and i cannot pass anything through nothing.

 

i dont even have a vfio.cfg file anymore.

 

Please PLEASE HELP

Looks like the one on group 15 is inuse by Unraid. Post diagnostics. If you don't have any of the check boxes ticked then there will be no vfio.cfg file.

  • Author

So when you see the file i put its a dual card but for some reason unraid is keeping it it is only passthrough 1 of the ports in the dual card

kilasnasrouter-diagnostics-20240219-1448.zip

Edited by kilasin

  • Community Expert

Looking at your logs, it seems to be eth2 is being enabled in bonding. Either turn off bonding or change the selection just to have ETH0 in the network settings.

 

Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link add name bond0 type bond mode 1 miimon 100
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth0 down
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth0 master bond0 up type bond_slave
Feb 19 06:29:06 KilasNasRouter kernel: eth0: 0xffffc90000760000, 
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth1 down
Feb 19 06:29:06 KilasNasRouter kernel: bond0: (slave eth0): Enslaving as a backup interface with a down link
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth1 master bond0 up type bond_slave
Feb 19 06:29:06 KilasNasRouter kernel: bond0: (slave eth1): Enslaving as a backup interface with a down link
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth2 down
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth2 master bond0 up type bond_slave
Feb 19 06:29:06 KilasNasRouter kernel: bond0: (slave eth2): Enslaving as a backup interface with a down link
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth3 down
Feb 19 06:29:06 KilasNasRouter rc.inet1: ip link set eth3 master bond0 up type bond_slave
Feb 19 06:29:06 KilasNasRouter kernel: pps pps2: new PPS source ptp2
Feb 19 06:29:06 KilasNasRouter kernel: ixgbe 0000:09:00.0: registered PHC device on eth3
Feb 19 06:29:07 KilasNasRouter kernel: bond0: (slave eth3): Enslaving as a backup interface with a down link
Feb 19 06:29:07 KilasNasRouter rc.inet1: ip link set name bond0 type bond primary eth0
Feb 19 06:29:07 KilasNasRouter rc.inet1: ip link add name br0 type bridge stp_state 0 forward_delay 0
Feb 19 06:29:07 KilasNasRouter kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Feb 19 06:29:07 KilasNasRouter rc.inet1: ip link set bond0 down
Feb 19 06:29:07 KilasNasRouter rc.inet1: ip -4 addr flush dev bond0
Feb 19 06:29:07 KilasNasRouter rc.inet1: ip link set bond0 master br0 up
Feb 19 06:29:07 KilasNasRouter kernel: br0: port 1(bond0) entered blocking state
Feb 19 06:29:07 KilasNasRouter kernel: br0: port 1(bond0) entered disabled state
Feb 19 06:29:07 KilasNasRouter kernel: device bond0 entered promiscuous mode
Feb 19 06:29:07 KilasNasRouter rc.inet1: ip link set br0 up
Feb 19 06:29:07 KilasNasRouter kernel: br0: port 1(bond0) entered blocking state
Feb 19 06:29:07 KilasNasRouter kernel: br0: port 1(bond0) entered forwarding state
Feb 19 06:29:07 KilasNasRouter kernel: br0: port 1(bond0) entered disabled state
Feb 19 06:29:09 KilasNasRouter kernel: igc 0000:04:00.0 eth2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 19 06:29:09 KilasNasRouter kernel: bond0: (slave eth2): link status definitely up, 1000 Mbps full duplex
Feb 19 06:29:09 KilasNasRouter kernel: bond0: (slave eth2): making interface the new active one
Feb 19 06:29:09 KilasNasRouter kernel: device eth2 entered promiscuous mode
Feb 19 06:29:09 KilasNasRouter kernel: bond0: active interface up!

  • Author

Also found this in the log but do not understand it 

 

image.thumb.png.9d4fff6bea9041f1e69d491c2edd7657.png

  • Author

i know that part but i tried using the pci e acs override using downstream (no avail) , Multi (no avail) , Both (no avail) ... 

it should have it own iommu group since both cards the rtl and the 225 are seperate

 

 

  • Author
  • Solution

well i tried a few things and i believe i got it to work thank goodness wow a whole day and a half with system down pretty much ...

 

So for anyone else having this trouble i will explain my steps on how to fix it.

 

1)unbind all nics from network settings 

2)go to settings/vm manager 

3)pci e aces override: multifunction only (you may try down frist then multi function then both)

4)vfio allow unsafe interrupts: Yes (no idea exactly what it does but it split my iommu up 

5)go to Tools/System Devices and check mark the pcis that you want to passthrough

6)click on bind selected to vfio

7)reboot 

 

Voila that is all ! thanks Simon for trying to help you pointed me in the right direction then i just tested stuff out myself until it worked not sure this is the most optimal solution but it worked for me. Please let me know what unsafe interrupt does if you dont mind. Thank !!!

 

Best Regards

Art

  • Community Expert
2 hours ago, kilasin said:

well i tried a few things and i believe i got it to work thank goodness wow a whole day and a half with system down pretty much ...

 

So for anyone else having this trouble i will explain my steps on how to fix it.

 

1)unbind all nics from network settings 

2)go to settings/vm manager 

3)pci e aces override: multifunction only (you may try down frist then multi function then both)

4)vfio allow unsafe interrupts: Yes (no idea exactly what it does but it split my iommu up 

5)go to Tools/System Devices and check mark the pcis that you want to passthrough

6)click on bind selected to vfio

7)reboot 

 

Voila that is all ! thanks Simon for trying to help you pointed me in the right direction then i just tested stuff out myself until it worked not sure this is the most optimal solution but it worked for me. Please let me know what unsafe interrupt does if you dont mind. Thank !!!

 

Best Regards

Art

Unsafe because the guest is able to send to the host. Normally virtualisation/Containerisation protects the host, but some hardware does not support that so you need this feature turned on.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.