Arch Linux

v1k1n

Member

Registered: 2011-10-13

Posts: 2

QEMU/KVM Passthrough -

I have setup a qemu/kvm passthrough gaming rig. Arch as the host and Win10 as the single guest. It works most of the time, but the windows guest crashes every now and then. When it crashes, I see these log messages:

WARNING: CPU: 4 PID: 2638 at drivers/pci/msi.c:972 pci_enable_msix+0x412/0x450()
.....
[<ffffffff8133e8de>] pci_enable_msix+0x3de/0x450
[<ffffffff8133e97c>] pci_enable_msix_range+0x2c/0x60
[<ffffffffa002a363>] vfio_pci_set_msi_trigger+0xf3/0x300 [vfio_pci]
[<ffffffffa002a9cf>] vfio_pci_set_irqs_ioctl+0x3f/0xa0 [vfio_pci]
[<ffffffffa0028efe>] vfio_pci_ioctl+0x2fe/0x9c0 [vfio_pci]
[<ffffffff8123b3eb>] ? eventfd_write+0xdb/0x250
[<ffffffff810a2a00>] ? wake_up_q+0x70/0x70
[<ffffffffa0000253>] vfio_device_fops_unl_ioctl+0x23/0x30 [vfio]
[<ffffffff812021e3>] do_vfs_ioctl+0xa3/0x5d0
[<ffffffff8120c5b7>] ? __fget+0x77/0xb0
[<ffffffff81202789>] SyS_ioctl+0x79/0x90
[<ffffffff816b56ae>] entry_SYSCALL_64_fastpath+0x12/0x6d

After that trace, I see this:

kernel: kernel BUG at drivers/pci/msi.c:368!
kernel: invalid opcode: 0000 [#1] PREEMPT SMP 
[<ffffffff8133e8de>] pci_enable_msix+0x3de/0x450
[<ffffffff8133e97c>] pci_enable_msix_range+0x2c/0x60
[<ffffffffa002a363>] vfio_pci_set_msi_trigger+0xf3/0x300 [vfio_pci]
[<ffffffffa002a9cf>] vfio_pci_set_irqs_ioctl+0x3f/0xa0 [vfio_pci]
[<ffffffffa0028efe>] vfio_pci_ioctl+0x2fe/0x9c0 [vfio_pci]
[<ffffffff8123b3eb>] ? eventfd_write+0xdb/0x250
[<ffffffff810a2a00>] ? wake_up_q+0x70/0x70
[<ffffffffa0000253>] vfio_device_fops_unl_ioctl+0x23/0x30 [vfio]
[<ffffffff812021e3>] do_vfs_ioctl+0xa3/0x5d0
[<ffffffff8120c5b7>] ? __fget+0x77/0xb0
[<ffffffff81202789>] SyS_ioctl+0x79/0x90
[<ffffffff815b56ae>] entry_SYSCALL_64_fastpath+0x12/0x6d
Code: 85 ff 74 29 41 8b 46 14 85 c0 74 21 31 db eb 0d 83 c3 01 41 39 5e 14 76 14 41 8b 7e 10 01 df e8 6c 33 d9 ff 48 83 78 70 00 74 e5 <0f> 0b 4d 8b 36 4d 39 f4 75 c7 49 8b bd 88 02                             
RIP  [<ffffffff8133e39b>] free_msi_irqs+0x5b/0x1c0
RSP <ffff88006aba3c88>

I'm running the latest packges, including standard kernel (no lts)

This may be a bug in the kernel or qemu, but I wanted to post here first and see if anyone is experiencing similar issues.