QEMU/KVM and GPU Passthrough Troubleshooting: Difference between revisions

From WikiMLT
Browse history interactively
← Older editNewer edit →
VisualWikitext
Spas (talk | contribs)
Image-reviewer, Public, Bots, Bureaucrats, Check users, Structured Discussions bots, Interface administrators, Oversighters, smwadministrator, smwcurator, Suppressors, Administrators, translator, Upload Wizard campaign editors, widgeteditor
31,253 edits
Spas (talk | contribs)
Image-reviewer, Public, Bots, Bureaucrats, Check users, Structured Discussions bots, Interface administrators, Oversighters, smwadministrator, smwcurator, Suppressors, Administrators, translator, Upload Wizard campaign editors, widgeteditor
31,253 edits
Line 19: Line 19:
</gallery>
</gallery>


I [[KVM_and_GPU_Passthrough_in_Details#Isolation_of_the_Guest_GPU|mentioned]] the kernel command <code>irqpool</code> as solution for this issue, but in my opinion and according to some other posts, provided in the references section, this setting is an actual solution for the problem <code>irq 44: nobody cared (try booting with the "irqpool" option); handlers: vfio_intx_handler; Disabling IRQ #44</code>, that appears at my system when booting a VM with GPU passthrough with a display attached to it, which was causing host system reboot.
I was [[QEMU/KVM and GPU Passthrough in Details#Isolation of the Guest GPU|mentioned]] the kernel command <code>irqpool</code> as solution for this issue, but in my opinion and according to some other posts, provided in the references section, this setting is an actual solution for the problem <code>irq 44: nobody cared (try booting with the "irqpool" option); handlers: vfio_intx_handler; Disabling IRQ #44</code>, that appears at my system when booting a VM with GPU passthrough with a display attached to it, which was causing host system reboot.


References:
References:

Revision as of 12:57, 2 September 2022

Guest GPU Au­dio Crack­ling and IRQ xx: No­body Cared Fix

The so­lu­tion of the is­sue Guest GPU HD­MI Au­dio Crack­ling, Bro­ken or Los­ing is well ex­plained by Jonp at UN­RAID Fo­rums. In short we must try to en­able the MSI – Mes­sage Sig­naled In­ter­rupts op­tion if the de­vice sup­port it. Here is a de­tailed step-by-step in­struc­tion how to do that.

  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 1: Open Device Manager and from the View menu switch to Resources by type.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 1: Open De­vice Man­ag­er and from the View menu switch to Re­sources by type.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 2: Expand the section Interrupt request (IRQ).
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 2: Ex­pand the sec­tion In­ter­rupt re­quest (IRQ).
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 3: Find the problematic audio device and by the context menu choice Properties.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 3: Find the prob­lem­at­ic au­dio de­vice and by the con­text menu choice Prop­er­ties.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 4: Within the Details tab witch to Property Device instance path.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 4: With­in the De­tails tab witch to Prop­er­ty De­vice in­stance path.
  • QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 5: In this par­tic­u­lar case the Val­ue is PCI­\­VEN­_­10­DE­&­DEV­_­0E­08­&­SUB­SYS­_­102­F10­DE­&­REV­_­A1­\­4&­29­fcb­422­&0­&00­16. This is a re­la­ti­ve path to Com­pu­ter­\­HKEY­_­LO­CAL­_­MA­CHI­NE­\­SYS­TEM­\­Cur­rent­Con­trol­Set­\­Enum in the Win­dows 10's regis­try.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 5: In this par­tic­u­lar case the Val­ue is PCI­\­VEN­_­10­DE­&­DEV­_­0E­08­&­SUB­SYS­_­102­F10­DE­&­REV­_­A1­\­4&­29­fcb­422­&0­&00­16. This is a re­la­ti­ve path to Com­pu­ter­\­HKEY­_­LO­CAL­_­MA­CHI­NE­\­SYS­TEM­\­Cur­rent­Con­trol­Set­\­Enum in the Win­dows 10's regis­try.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 6: Run Registry Editor as Administrator.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 6: Run Reg­istry Ed­i­tor as Ad­min­is­tra­tor.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 7: In the Registry Editor tool, paste Com­pu­ter­\­HKEY­_­LO­CAL­_­MA­CHI­NE­\­SYS­TEM­\­Cur­rent­Con­trol­Set­\­Enum in the path line and hit Enter.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 7: In the Reg­istry Ed­i­tor tool, paste Com­pu­ter­\­HKEY­_­LO­CAL­_­MA­CHI­NE­\­SYS­TEM­\­Cur­rent­Con­trol­Set­\­Enum in the path line and hit En­ter.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 8: In Device Manager, use the context menu and Copy the Value of the target Device instance path.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 8: In De­vice Man­ag­er, use the con­text menu and Copy the Val­ue of the tar­get De­vice in­stance path.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 9: In Registry Editor append one backslash to the path and Paste the Value.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 9: In Reg­istry Ed­i­tor ap­pend one back­slash to the path and Paste the Val­ue.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 10: In Registry Editor, navigate to \Device Parameters\Interrupt Ma­na­ge­ment\Me­ssa­ge­Sig­na­led­In­ter­rupt­Pro­per­ties.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 10: In Reg­istry Ed­i­tor, nav­i­gate to \De­vice Parameters\Interrupt Ma­na­ge­ment\Me­ssa­ge­Sig­na­led­In­ter­rupt­Pro­per­ties.
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 11: Then choose Modify from the context menu the Value of the DWORD Key MSISupported (MSI – Message Signaled Interrupts).
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 11: Then choose Mod­i­fy from the con­text menu the Val­ue of the DWORD Key MSISup­port­ed (MSI – Mes­sage Sig­naled In­ter­rupts).
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 12: Change the Value of the DWORD Key MSISupported to 1 [0x0..01].
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 12: Change the Val­ue of the DWORD Key MSISup­port­ed to 1 [0x0..01].
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 13: Confirm the change of the DWORD Key MSISupported (MSI – Message Signaled Interrupts).
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 13: Con­firm the change of the DWORD Key MSISup­port­ed (MSI – Mes­sage Sig­naled In­ter­rupts).
  • QEMU KVM Windows Guest Fix NVIDIA NVS 315 HDMI Audio Step 14: Reboot the guest Operating system.
    QE­MU KVM Win­dows Guest Fix NVIDIA NVS 315 HD­MI Au­dio Step 14: Re­boot the guest Op­er­at­ing sys­tem.

I was men­tioned the ker­nel com­mand irqpool as so­lu­tion for this is­sue, but in my opin­ion and ac­cord­ing to some oth­er posts, pro­vid­ed in the ref­er­ences sec­tion, this set­ting is an ac­tu­al so­lu­tion for the prob­lem irq 44: no­body cared (try boot­ing with the "irqpool" op­tion); han­dlers: vfio_​​​intx_​​​handler; Dis­abling IRQ #44, that ap­pears at my sys­tem when boot­ing a VM with GPU passthrough with a dis­play at­tached to it, which was caus­ing host sys­tem re­boot.

Ref­er­ences:

Retrieved from "https://wiki.metalevel.tech/index.php?title=QEMU/KVM_and_GPU_Passthrough_Troubleshooting&oldid=30990"