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.

QEMU PCI IRQ Handler Assertion Failure

  • Urgent

When attempting to pass through the 8111 network interface (Realtek RTL8111) to a virtual machine running on Unraid, the VM fails to start and QEMU throws an assertion failure related to PCI IRQ handling:

internal error: QEMU unexpectedly closed the monitor (vm='openwrt'): qxl_send_events: spice-server bug: guest stopped, ignoring qemu-system-x86_64: ../hw/pci/pci.c:1633: pci_irq_handler: Assertion 0 <= irq_num && irq_num < PCI_NUM_PINS' failed.

Steps to Reproduce:

Configure a virtual machine in Unraid.

Pass through the 8111 network interface (Realtek RTL8111) to the VM.

Start the virtual machine.

The VM fails to launch, and the error message appears in the log.

Expected Behavior:
The virtual machine should start successfully with the 8111 network interface passed through, without any errors related to PCI IRQ handling.

Actual Behavior:
The virtual machine fails to launch, and QEMU throws an assertion failure related to pci_irq_handler in pci.c.

Environment:

Host OS: Unraid

Guest OS: OpenWrt

Network Interface:

8125 (used for host connectivity)

8111 (passed through to VM, causing error)

Logs:

Feb 6 13:54:00 mewtwo rc.docker: Containers started.

Feb 6 13:55:40 mewtwo kernel: br0: port 2(vnet0) entered blocking state

Feb 6 13:55:40 mewtwo kernel: br0: port 2(vnet0) entered disabled state

Feb 6 13:55:40 mewtwo kernel: vnet0: entered allmulticast mode

Feb 6 13:55:40 mewtwo kernel: vnet0: entered promiscuous mode

Feb 6 13:55:40 mewtwo kernel: br0: port 2(vnet0) entered blocking state

Feb 6 13:55:40 mewtwo kernel: br0: port 2(vnet0) entered forwarding state

Feb 6 13:55:41 mewtwo kernel: pcieport 0000:00:1c.1: broken device, retraining non-functional downstream link at 2.5GT/s

Feb 6 13:55:42 mewtwo kernel: pcieport 0000:00:1c.1: retraining failed

Feb 6 13:55:43 mewtwo kernel: pcieport 0000:00:1c.1: Data Link Layer Link Active not set in 1000 msec

Feb 6 13:55:44 mewtwo kernel: pcieport 0000:00:1c.1: Data Link Layer Link Active not set in 1000 msec

Feb 6 13:55:44 mewtwo kernel: vfio-pci 0000:03:00.0: Unable to change power state from D0 to D3hot, device inaccessible

Feb 6 13:55:44 mewtwo kernel: br0: port 2(vnet0) entered disabled state

Feb 6 13:55:44 mewtwo kernel: vnet0 (unregistering): left allmulticast mode

Feb 6 13:55:44 mewtwo kernel: vnet0 (unregistering): left promiscuous mode

Feb 6 13:55:44 mewtwo kernel: br0: port 2(vnet0) entered disabled state

Feb 6 13:55:44 mewtwo kernel: vfio-pci 0000:03:00.0: Unable to change power state from D3cold to D0, device inaccessible

Feb 6 13:55:44 mewtwo kernel: vfio-pci 0000:03:00.0: Unable to change power state from D3cold to D0, device inaccessible

Feb 6 13:55:50 mewtwo kernel: vfio-pci 0000:03:00.0: Unable to change power state from D3cold to D0, device inaccessible 

 

 

After a while of system startup, the 8111 graphics card displays "Unknown header type 7f"  and The error message when creating a virtual machine changes to ‘internal error: Unknown PCI header type '127' for device '0000:03:00.0'

 

20250206135948.png

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.