Replying to Avatar Dr. Hax

nostr:npub1f6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4kslazcka, you are a fellow #QubesOS user, do you know of any reason why I would be able to `qvm-device mic attach foobar dom0:mic` just fine but no mic audio shows up in the VM?

- Audio shows up in dom0

- Attach has a rc of zero

- Worked on Tuesday

- Template VMs are the stock Debian and Fedora images

🤔🧐

Should I see anything in dmesg in the VM when I attach the mic, or is that transparent to the guest?

what do you see when you run 'qvm-device mic list' in dom0?

try making it persistent

'qvm-device mic attach --persistent foobar dom0:mic'

Reply to this note

Please Login to reply.

Discussion

are you not seeing your mic in devices (gui) at all?

`qvm-device mic list` shows the mic

Using --persistent functioned the same as without that flag (rc=0, no mic audio in qube). How do I undo that? Detach tells me persistent devices can't be detached while the qube is running and with the qube shut down it tells me "pulseaudio agent not running".

I see the mic in dom0 and I see levels there. I see the mic in the qube's GUI, but it's not selected by default, I can select the device, turn the volume slider up, but it looks like it's muted and that button is disabled. Pics attached below.

I also found that I don't have /etc/qubes/policy.d/50-sys-audio.policy in dom0, but I'm not sure if that was only present in an old version of Qubes. I saw a reference to it here: https://forum.qubes-os.org/t/unable-to-passthrough-audio-device-to-sys-audio/9684

Here's dom0, working like a champ:

#m=image%2Fjpeg&dim=633x331&blurhash=i1R3Wftn4n%25h00-mRjRiRi00D%25Dhp0%3Fa%25LtRIU%25M00%7Eq%5E%2BD*oHIUNHWEae008_IV00%252oyRPx%5DM_00S6-%3FIU%3FaxtxVxuM%7B&x=7990f9b2646b83831ced61b3a729ab04a5080ed84f347f4a7fa9010ad455c700

The default view when I open the system settings in the qube:

#m=image%2Fjpeg&dim=990x670&blurhash=r0Rp8-000000004n00t80000-ooISj-%3A-%3BE1bH%25L00n%7D%3Fbo%23%25Ms%3A%3Fbt7ay009F9F%3Fb%25M-%3BM%7BRkt700x%5D%25M%25LtRt7%25MRjt7004o4.xY.8%3FbRjWBt7&x=66c90d7d460703920782b5e3a3be6d36f12d309147b15bf338d3d50df240617f

And the best I can do with making the qube's setting be what I want:

#m=image%2Fjpeg&dim=990x670&blurhash=r0Rp8-8%5E0000008_00a%7D0000t6Rj-%3B%25M%25MIUWBxu00ac%3FHx%5D%252j%40%3Fbxuf600M_ITXA%3FH%3FbIUWCt700SPtR%5E*R.of%25MWBoz008_4nt7%3Fb%3FbWBWBt7&x=cbbb0c21934bef5fc6ce964f88dd430e4208036fd6c3016d2af267a878f37603

Tagging nostr:npub1f6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4kslazcka in case it they missed my last reply

hmmm, looks like the detach persistent device bug is still persistent in 4.2

go to

/var/lib/qubes/qubes.xml

set mic device to null

save and reboot

all good?

*in dom0 ofc

4.2 introduced pipewire, but it's not officially supported in dom0

https://github.com/qubesos/qubes-issues/issues/6358#issuecomment-1712130215

some have reported a temporary fix

https://forum.qubes-os.org/t/4-2-sound-issue-and-temporary-fix/23095

but check this out before you go removing pipewire

https://forum.qubes-os.org/t/v4-2-pipewire-installation/19140

unfortunately i'm super busy atm and can't speak to your specific issue/hardware, but check this out as well

https://forum.qubes-os.org/t/qubes-4-2-audio-issues-need-to-reset-audio-output-for-each-new-qube-audio-use/19921/2

lmk how you go

I found the docs on how Qubes gets audio from and to VMs. https://www.qubes-os.org/doc/audio-virtualization/ and I have a pacat-simple-vchan process running (in dom0) for each vm, I have the UNIX sockets in dom0 as well, so everything looks reasonable there. In the VMs, I can see pulseaudio running, and audio played in a VM comes out the speakers, so audio transmission seems to be working fine in that direction...

I've given up for now and am using my Acusis Echo-Cancelling Microphone Array, which is a USB device that passes through just fine (just like all my other USB devices).

thx for the update. now i get your setup. glad you've got a fallback mic that works as it should. what was the one that was giving you trouble?