| 1 | = Investigating audio problems = |
| 2 | |
| 3 | == Collecting information from the host == |
| 4 | |
| 5 | 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: |
| 6 | |
| 7 | '''Tip of the day''': Best is to copy & paste the following commands to avoid typing errors. |
| 8 | |
| 9 | * Shut down all VM instances and !VirtualBox programs, including VBoxSVC. |
| 10 | 1. On '''Windows''', run |
| 11 | {{{ |
| 12 | 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" /M |
| 13 | }}} |
| 14 | on an Administrator command prompt to set this on a system-wide level (required).[[br]][[br]] |
| 15 | 2. On POSIX-enabled hosts like '''Linux, Unix or OS X (MacOS)''', open or run a terminal as '''root''' and run |
| 16 | {{{ |
| 17 | export 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 |
| 18 | }}} |
| 19 | |
| 20 | * Close the Administrator / root terminal |
| 21 | * Open a new terminal as '''regular user'''[[br]][[br]] |
| 22 | 1. On '''Windows''', verify that the changes were applied correctly be running |
| 23 | {{{ |
| 24 | echo %VBOX_RELEASE_LOG% |
| 25 | }}} |
| 26 | 2. On POSIX-enabled hosts like '''Linux, Unix or OS X (MacOS)''' verify that the changes were applied correctly be running |
| 27 | {{{ |
| 28 | env | grep VBOX_RELEASE_LOG |
| 29 | }}} |
| 30 | * Start the !VirtualBox Manager and start the VM you want to diagnose audio for. |
| 31 | * Perform and reproduce the audio operation. |
| 32 | |
| 33 | |
| 34 | == Ok, all done! What now? == |
| 35 | |
| 36 | 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 [https://www.virtualbox.org/wiki/Bugtracker public bug tracker]. |
| 37 | |
| 38 | '''Note:''' Without the log file we cannot diagnose your issue, so please make sure to always attach that. Thank you. |
| 39 | |
| 40 | |
| 41 | |