KVM SR-IOV devices with high latency and messages like "Spurious APIC interrupt (vector 0xFF) on CPU#0, should never happen"

Solution Verified - Updated -


  • Virtual Machine dmesg shows many errors such as below:
Spurious APIC interrupt (vector 0xFF) on CPU#0, should never happen.
  • Virtual Machine takes a very long time to initialise SR-IOV devices on reboot, or hangs.
  • SR-IOV Network Interfaces have high latency after a Guest reboot


  • Red Hat Enterprise Linux 9.2 KVM Host
  • nVidia GPU Passthrough to KVM Guest
  • SR-IOV NIC passthrough to KVM Guest (eg: Intel, Mellanox, Broadcom, etc)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content