So I have this sound problem with my win10 kvm. I know it’s a common problem but I have problems to really understand all the consequences of this problem.
So I got my usb headset which has been confirmed to me by technical support that the AMP (it’s A40 astro gaming mixamp) is acting as a soundcard, so I add the usb headset as the other devices like keyboard and mouse but apparently for the sound it’s not enough? Because I got cracky noise all the time in the headset.
And from what I fell from that thread is that I need to use the pci-stub, is it correct?
Does someone know why we need pci-stub? does the keyboard and mouse have more latency than the sound?
Do I still need to put the soundcard as ac97 in the vm? Because I can’t get it working apparently, I can’t install the drivers even with signature enforcement off. To which problem is that related to?
Thanks in advance for all the help/explanation you can provide.
yeah i use only usb2 with the headset.
and for the drivers I don’t really think so but I’m not sure it’s pretty plug and play
that’s why I’m surprised.
I will try those software mitigation if I find enough documentation to actually do it since most of the time is a bit harsh on that one
so I’ve isolate the cores of the cpu using that:
GRUB_CMDLINE_LINUX=“resume=/dev/mapper/fedora_localhost–live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap intel_io
mmu=on rd.driver.pre=vfio-pci rhgb quiet isolcpus=4-7 nohz_full=4-7 rcu_nocbs=4-7”
I’m not sure it works since I can see really low activity on the last 4 cores but not same activity as the same first.
But my Vm is now only using one core and I have done this :
Then, run qemu-system-x86_64 with taskset and chrt:
chrt -r 1 taskset -c 4-7 qemu-system-x86_64 …
The chrt command will ensure that the task scheduler will round-robin distribute work (otherwise it will all stay on the first cpu). For taskset, the CPU numbers can be comma- and/or dash-separated, like “0,1,2,3” or “0-4” or “1,7-8,10” etc.
from https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#CPU_pinning