Investigating audio problems
Collecting information from the host
As always when it comes to diagnosing problems with VirtualBox the appropriate VBox.log is useful to have. To gather more verbose information about the actual audio state, please do the following:
Tip of the day: Best is to copy & paste the following commands to avoid typing errors.
- On Windows
- Shut down all VM instances and VirtualBox programs, including VBoxSVC.
setx VBOX_RELEASE_LOG "drv_host_audio.e.l.l2.l3.f+drv_audio.e.l.l2.l3.f+audio_mixer.e.l.l2.l3.f+dev_hda_codec.e.l.l2.l3.f+dev_hda.e.l.l2.l3.f+dev_ac97.e.l.l2.l3.f" /Mon an Administrator command prompt to set this on a system-wide level (required).
- Close the Administrator terminal
- Open a new terminal as regular user
- verify that the changes were applied correctly be running
- Start the VirtualBox Manager.
- On Linux/OS X/Solaris, stop the VirtualBox manager and restart it by running the following from a terminal:
- Start the machine you want to diagnose audio for.
- Perform and reproduce the audio operation.
Important: The newly created VBox.log log file must contain the line
Audio: Verbose logging enabled
Ok, all done! What now?
Please collect the VBox.log from the host, pack it (ZIP, RAR) into an archive and submit that archive as part of a new or existing bug report at our public bug tracker.
Note: Without the log file we cannot diagnose your issue, so please make sure to always attach that. Thank you.