AFAIK, there is no straightforward way at the moment. Audio is handled by dom0, while USB/Bluetooth is usually handled by a special AppVM (and and especially Bluetooth shouldn't be handled by dom0). Maybe it will not be hard to implement delegating audio to an AppVM, but it will require studying the problem etc. There is a related Github ticket: https://github.com/QubesOS/qubes-issues/issues/1590
Without that, you can run your sound from one VM (not necessarily sys-usb), but it would send sound from that one VM only, not globally. I've configured one VM to route sound through another VM via PulseAudio over network. If you are interested, I can tell you more details. This still does not resolve Bluetooth audio fully (you cannot connect dom0 to it, as there is no network and there shouldn't be one) and it probably adds some attack surface via the PulseAudio protocol etc., but it at least doesn't require you to have one SoundEintopfVM where you run all audio-related tasks. Some older discussion thread related to sound output from AppVM: https://groups.google.com/forum/m/#!topic/qubes-users/DFPGkGmAnjI Regards, Vít Šesták 'v6ak' -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8344d239-0491-4ca5-b40c-a3bfcbe9faff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
