I have a USB microphone that can plug and play on the opensuse host. Now I add the usb device via virt-manager to the win10 guest created with qemu/kvm.
I can see the microphone name as the audio input device in win10, but no program can actually receive any audio input from the microphone.
Win10 troubleshoot can’t find any problem. If I use audacity, when I press record, it shows “error opening recording device. Error code, -9999 unanticipated host error.”
After a few hours of research I still can’t make it work.
Yes. And the device name appears in every program as an audio input device as well. But all the programs just complain there is something wrong with it when I try to use it to receive voice input.
lsusb
...
Bus 005 Device 008: ID 17a0:0310 Samson Technologies Corp. Meteor condenser microphone
...
Then I use virt-manager for the guest, “Add new virtual hardware” -> “USB Host Device” -> pick “005:008 Samson Technologies Corp. Meteor condenser microphone”
After that USB 17a0:0310 is shown in the list of the guest machine hardware in the virt-manager GUI.
If I boot into Win10, in there it shows I have a Samson Meteor microphone, except that it doesn’t work.
edit: Oh for your previous question, I just found out that when win10 guest is open, this microphone is not shown in the host any more.
I also just followed the instruction on the page for “recognition issue” on windows, but if I “uninstall usb device -> unplug device -> reboot win10 ->plug in device”, the guest won’t
have this device enabled at all for the guest machine, since I assume I need to have it plugged in before booting the guest machine.
So this probably is an issue for the specific device and unrelated to qemu/kvm virtualization?
The next step is to understand that you are trying to set up a USB pass-through.
A prime feature of hardware pass-through is that it’s no longer available to the HostOS or any other Guest, so a Quick and Dirty check is whether you can use the microphone in the HostOS… If you can, then you know you haven’t set it up correctly for your Guest.
The following is likely your best guide on the Internet, it describes setting up both by command line and using vm-manager
If you can verify the above is done correctly, it should at least more or less ensure that you’ve set up Guest access correctly, and can then turn your attention to whether there is an issue in Windows, ie Is a special driver for this device required? Typical tries are to enable Windows Update to install drivers for third party software, and if a driver is downloadable from the manufacturer, then you can install that.
It seems this has nothing to do with linux/qemu/kvm/virtualization now. I have a dual boot win10 that I haven’t boot into for some time. So I went there and found out the mic had similar issue. The device name is shown everywhere but all recording programs can’t work with it.
At the moment this mic only works on opensuse, and very well actually.
In fact some strange thing happened to the mic a few months ago, when it stopped working completely and displayed a weak red light. Then I used the tool provided by the vendor to flash its firmware. It worked at first, but later it seemed to break every time I have a reboot of the machine (opensuse only). It seemed to me each opensuse boot would corrupt its firmware. I don’t remember exactly what I did but I might have changed the usb port it was plugged into, as the problem stopped occurring later.
That was a bit of history of it.
BTW, now even in win10 the firmware flashing tool could not work as it says “can’t connect(detect) the mic”.
As paranoid as I am, I suspect this mic is being manipulated by some malware on the system, because it’s working great on my main OS opensuse…