&@*&$&@!! Here is why sound on Linux is a mess: http://tuxradar.com/content/how-it-works-linux-audio-explained
Basically, in KDE4, we have phonon running on top of pulseaudio, running on top of alsa - and all of them can interact with user processes.
Here is my situation and attempt to troubleshoot:
Host: Debian 8: kernel 3.16
virtualbox 5.1.8 (jessie-backports)
pulseaudio 7.1 (jessie-backports)
Guest: Whonix 13 Workstation
virtualbox-guest-x11 5.1.8 (jessie-backports)
pulseaudio: not installed
When the VM is set to use Host Audio Driver: Pulseaudio, no sound works in VM. I have no idea why. Maybe it requires pulseaudio in the guest? In any case, first step should be getting sound through alsa.
Change Host Audio Driver to ALSA Audio Driver and now all alsa related functions should work in the guest, including your test command: aplay. The test functions in System Settings > Multimedia should also work. VLC should also work. useful commands: alsamixer, aplay
Sound does not work in Tor Browser. According to , firefox will eventually make pulseaudio a hard dependency. Requirement may already be downstreamed to Tor Browser (don’t know). So install pulseaudio (other useful packages: pavucontrol, paman). useful commands: pavucontrol, paman, pavumeter, pactl. Sound now works in Tor Browser.
Switch Host Audio Driver back to Pulseaudio and it still doesn’t work. Who the hell knows…
I would agree with that.
I don’t know how to do that. I have the same messages in dmesg as you, but my sound is now working. I would guess that is not the culprit.
Does Host Audio Driver: Pulseaudio work when using virtualbox, pulseaudio from Debian stable?
@Patrick Given , we may need to install pulseaudio by default in Whonix. I think it was removed from Whonix 12 → Whonix 13.