nightrider9870 Posted March 11, 2021 Share Posted March 11, 2021 (edited) Hello, So I updated to 6.9 a few days ago and this brought huge stability issues on W10VM. After doing some reading I saw that people fixed the issue by adjusting a setting in the tips and tweaks section (setting the cpu to performance and enabling turbo) luckily I had done this prior so that wasn't the issue. Then I saw that removing the appended vfio devices in the boot config and adding the devices via the tools section should help, I did this and like that we can more easily do this now but still that didn't fix it at all. So now I'm stuck, the main issue I'm having is cpu interrupts that make the system stutter a lot. I'm not really sure what to do now. I did update the windows drivers thinking it might help, but of course it didn't. I also updated to 6.9.1 to see if that would work. Any help would be greatly appreciated. I have attached my diagnostics for viewing along with a copy of my vm-xml. Also a copy of the logs straight from the dash below. Mar 10 17:18:37 Icarus kernel: vfio-pci 0000:17:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Mar 10 17:18:37 Icarus kernel: vfio-pci 0000:03:00.0: vfio_ecap_init: hiding ecap 0x1e@0x180 Mar 10 17:18:39 Icarus kernel: vfio-pci 0000:05:00.0: vfio_ecap_init: hiding ecap 0x19@0x200 Mar 10 17:18:40 Icarus kernel: vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0x19@0x200 Mar 10 17:18:40 Icarus kernel: vfio-pci 0000:07:00.0: vfio_ecap_init: hiding ecap 0x19@0x168 Mar 10 17:18:40 Icarus kernel: vfio-pci 0000:07:00.0: vfio_ecap_init: hiding ecap 0x1e@0x190 Mar 10 17:18:43 Icarus kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Mar 10 17:18:43 Icarus kernel: CPU: 18 PID: 0 Comm: swapper/18 Tainted: G I 5.10.21-Unraid #1 Mar 10 17:18:43 Icarus kernel: Hardware name: Gigabyte Technology Co., Ltd. X299 AORUS Gaming 7/X299 AORUS Gaming 7, BIOS F9k 11/06/2018 Mar 10 17:18:43 Icarus kernel: Call Trace: Mar 10 17:18:43 Icarus kernel: <IRQ> Mar 10 17:18:43 Icarus kernel: dump_stack+0x6b/0x83 Mar 10 17:18:43 Icarus kernel: __report_bad_irq+0x30/0xa5 Mar 10 17:18:43 Icarus kernel: note_interrupt+0x1d8/0x229 Mar 10 17:18:43 Icarus kernel: handle_irq_event_percpu+0x4f/0x6f Mar 10 17:18:43 Icarus kernel: handle_irq_event+0x34/0x51 Mar 10 17:18:43 Icarus kernel: handle_fasteoi_irq+0x7f/0xe6 Mar 10 17:18:43 Icarus kernel: asm_call_irq_on_stack+0x12/0x20 Mar 10 17:18:43 Icarus kernel: </IRQ> Mar 10 17:18:43 Icarus kernel: common_interrupt+0xa5/0x12e Mar 10 17:18:43 Icarus kernel: asm_common_interrupt+0x1e/0x40 Mar 10 17:18:43 Icarus kernel: RIP: 0010:arch_local_irq_enable+0x7/0x8 Mar 10 17:18:43 Icarus kernel: Code: 00 48 83 c4 28 4c 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 9c 58 0f 1f 44 00 00 c3 fa 66 0f 1f 44 00 00 c3 fb 66 0f 1f 44 00 00 <c3> 55 8b af 28 04 00 00 b8 01 00 00 00 45 31 c9 53 45 31 d2 39 c5 Mar 10 17:18:43 Icarus kernel: RSP: 0018:ffffc9000018fea0 EFLAGS: 00000246 Mar 10 17:18:43 Icarus kernel: RAX: ffff8888800a2380 RBX: 0000000000000003 RCX: 000000000000001f Mar 10 17:18:43 Icarus kernel: RDX: 0000000000000000 RSI: 0000000026a5b909 RDI: 0000000000000000 Mar 10 17:18:43 Icarus kernel: RBP: ffffe8ffff0b1f00 R08: 0000021450403a16 R09: 0000021452e4875c Mar 10 17:18:43 Icarus kernel: R10: 000000007fffffff R11: 071c71c71c71c71c R12: 0000021450403a16 Mar 10 17:18:43 Icarus kernel: R13: ffffffff820c7ec0 R14: 0000000000000003 R15: 0000000000000000 Mar 10 17:18:43 Icarus kernel: cpuidle_enter_state+0x101/0x1c4 Mar 10 17:18:43 Icarus kernel: cpuidle_enter+0x25/0x31 Mar 10 17:18:43 Icarus kernel: do_idle+0x1a6/0x214 Mar 10 17:18:43 Icarus kernel: cpu_startup_entry+0x18/0x1a Mar 10 17:18:43 Icarus kernel: secondary_startup_64_no_verify+0xb0/0xbb Mar 10 17:18:43 Icarus kernel: handlers: Mar 10 17:18:43 Icarus kernel: [<00000000d2f368e4>] i801_isr [i2c_i801] Mar 10 17:18:43 Icarus kernel: [<00000000ffa29e32>] vfio_intx_handler Mar 10 17:18:43 Icarus kernel: Disabling IRQ #16 icarus-diagnostics-20210310-1732.zip windows10-VMConfBackup.txt Edited March 11, 2021 by nightrider9870 Quote Link to comment
DoeBoye Posted March 11, 2021 Share Posted March 11, 2021 Can you try without passing through your rtx2080? Just use VNC. Obviously not a solution, but may help isolate the issue. I have the same problem, but if I don't pass through my video card, stability returns. 1 Quote Link to comment
nightrider9870 Posted March 12, 2021 Author Share Posted March 12, 2021 Thanks for the recommendation. I gave it a try, but it seems like cpu interrupt is still showing up and a lot of stuttering is seen. I might try reloading my windows 10 os, but that may have to wait till next week. This seems unlikely since the VM was working really well before the update and it seems to work fine if i boot to the NVMe drive. Quote Link to comment
nightrider9870 Posted March 12, 2021 Author Share Posted March 12, 2021 (edited) Small update, I found a good stackoverflow thread that addresses the "kernel: irq 16: nobody cared (try booting with the "irqpoll" option)" error that I'm seeing in the logs. When I have chance I will try to implement their solutions, but I'm curious if anyone else has seen this error before? If anyone is interested here is the forum I found. https://stackoverflow.com/questions/13861282/understanding-kernel-message-nobody-cared-try-booting-with-the-irqpoll-optio Edited March 12, 2021 by nightrider9870 Quote Link to comment
nightrider9870 Posted March 20, 2021 Author Share Posted March 20, 2021 Update. I had to revert back to 6.8.3. For whatever reason I am unable to get 6.9.1 to handle a windows 10 VM without massive stuttering. If anyone has helpful advice, please let me know. Thanks in advanced. Quote Link to comment
DoeBoye Posted March 21, 2021 Share Posted March 21, 2021 On 3/19/2021 at 11:32 PM, nightrider9870 said: Update. I had to revert back to 6.8.3. For whatever reason I am unable to get 6.9.1 to handle a windows 10 VM without massive stuttering. If anyone has helpful advice, please let me know. Thanks in advanced. I had a similar issue. This is what I did to solve the problem. You probably can skip right to the msi_util step, but I outlined everything I did, just in case... 1 Quote Link to comment
nightrider9870 Posted May 3, 2021 Author Share Posted May 3, 2021 On 3/21/2021 at 11:13 AM, DoeBoye said: I had a similar issue. This is what I did to solve the problem. You probably can skip right to the msi_util step, but I outlined everything I did, just in case... I completely appreciate the reply. My life got busy and I didn't have time to try this fix for a while. I just tried it today, and unfortunately no dice. I can't seem to figure out what's going on but as of right now update 6.9 and up is not useable for me. It's very odd since in version 6.8.3 I had no problems and my primary vm ran super responsively and now something in the update is causing issues. Quote Link to comment
Recommended Posts
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.