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 6.12.1 install I get vfio-pci-errors on startup

Featured Replies

After installing 6.12 I started getting these errors on boot up in the GUI. It will show a red alert error with:

 

VM Autostart disabled

vfio-pci-errors

VM Autostart disabled due to vfio--bind error

 

I have two VMs one of which auto starts and I bound a sound card and I believe a core or two to it in Tools --> System devices. I am able to start it once I get the system up and booted but seeing this errors makes me wonder if I should be handling this a different way?

Solved by SimonF

  • Community Expert
2 hours ago, severanced said:

After installing 6.12 I started getting these errors on boot up in the GUI. It will show a red alert error with:

 

VM Autostart disabled

vfio-pci-errors

VM Autostart disabled due to vfio--bind error

 

I have two VMs one of which auto starts and I bound a sound card and I believe a core or two to it in Tools --> System devices. I am able to start it once I get the system up and booted but seeing this errors makes me wonder if I should be handling this a different way?

have you checked the errors in the file. If you uncheck one entry and then reapply it will rebuild the vfio file

  • Author

To add to this, I was also curious because I'm in the middle of buying new hardware (motherboard, CPU, memory) to upgrade everything and I was worried about this error and being able to upgrade and start things up normally.

  • Community Expert
7 minutes ago, severanced said:

To add to this, I was also curious because I'm in the middle of buying new hardware (motherboard, CPU, memory) to upgrade everything and I was worried about this error and being able to upgrade and start things up normally.

Are the correct devices set correctly in tool ->sysdevs?

 

It is recommended to remove vfio mappings when changing hardware as pci numbers may change.

 

Uncheck on dev is sysdevs bind then recheck and bind and it should be fixed.

  • Author
2 hours ago, SimonF said:

Are the correct devices set correctly in tool ->sysdevs?

 

It is recommended to remove vfio mappings when changing hardware as pci numbers may change.

 

Uncheck on dev is sysdevs bind then recheck and bind and it should be fixed.

I'm not sure how to check that since none of my hardware has changed.

  • Community Expert
  • Solution
5 hours ago, severanced said:

I'm not sure how to check that since none of my hardware has changed.

image.png

Just change one of the tick boxes then press bind button and then revert that change and press bind again and it will fix the file.

  • Author

Thanks, I unchecked those, rebooted my system, then checked them and rebooted again and it seems to have cleared the red error.

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.