[Regression] No microphone, Windows Guest, Linux Host.

Description

Linux Host

Ubuntu 16.04

Kernel 4.7.0-040700-generic

Guest: Windows 8.1 (also appears to affect any other guest)

Audio Controller: Intel HD Audio

Microphone is enumerated by the guest, but it is always silent. On occasions fiddling with microphone driver enumeration (i.e. toggling "Show unplugged recording devices" several times, going to its properties, etc) can even crash VirtualBox (rare, happened to me only twice).

PulseAudio shows VirtualBox has requested and received microphone and speaker.
I've also tried the ALSA driver, same result. Couldn't try OSS driver (immediately aborts VM, didn't look much into it; I assumed either I had a missing dependency or the OSS device couldn't be grabbed)

I'm having the same issue after virtualbox update. I'm using Arch Linux and virtualbox guest utils and Windows 10 as Host. If I put Intel HD works, but the sound come oddly like an echo or a little delay (if you are watching an youtube video). In my case if I change back to AC97 works normal with a little delay. (Arch Linux LTS - KDE Plasma 5) Logs.zip

On my Arch Linux Gnome I'm having diferent situations... AC97 not working after reboot Logs.2.zip

I have same audio issue when I use Windows 10 host and run the Linux Guest (Ubuntu 16.04) on Virtualbox 5.0.26 and Virtualbox 5.1.2 (5.1.4).

I have test the the audio emulation settings, AC97 and IntelHD

Audio input and output are both workable, but the guest OS crash (freeze, and one thing I can do is force interrupt by the window close button [X] ) sometimes when I use pyaudio to start record audio. Not every time but randomly happen.

Audio output is workable but the audio input is not, when I test by Ubuntu audio setting, I can not see any sound pressure when I make noise.

And another. I'm using Adobe Captivate in a windows VM. In VB 5.0 the sound passed through to the application is pretty bad, lots of clicks are heard when sound volume is high. I'll upgrade to 5.1.4 to get rid of all this, I thought. Unfortunately the mic just doesn't work at all now.

with test build microphone works, but not well - without any change in settings or sound levels microphone volume bars in skype setings and gotomeeting sound check showed that I was speaking, but other side was not hearing me. when i touched volume settings in both host and guest it started to work, but my voice sounded like robot with lot of skips

btw sound is not good in general, lot of noise like old vinyl. in linux host everything is clean, from windows 10 guest it is always noisy regardless of volume levels set both in guest and host. but it was like this even in 5.x so it is not directly related to this issue

I have similar results. There's indication of sound, but barely. Can't make out words. Used a Skype for Business test call to test. Had Linux mic on full, Skype about 50%. Host is Mint LMDE 64 bit/16GB RAM and client is Win7 64bit with 6GB Ram. Same issue, 5.1.2/.4 no sound, 5.0 was capable of using Skype for Business.

I have gone back to 5.0.26 and replayed the exact same sequence. Sound from microphone was perfect. One thing I noticed however, is that the windows start-up tune seems a little longer in duration on 5.0.26 than on 5.1.4. On the latter, it seems almost cut-off, although subsequent sounds sound fine. It is just the start-up tune. This might be related, or due to improved speed of 5.1.4. I can't tell.

15806 is something I have noticed also, but for me started with 5.1.2, the first 5.1 version I tried. The others report a change from 5.1.2 to 5.1.4 in audio out. In my case I have not experienced this at all. VB does sometimes crap up all audio, something I put down to the host process not doing the resume well, something I can remember all the way back to 4 series. So perhaps the same reason microphones almost never make it is the same why speakers sometimes sound really bad. Interesting......

My apps which use the mic report there isn't one
When I try to set one up the diagnostic thingy comes up and thinks for awhile and finds that the mic is detected (even that it's a headset mic) but not ready and that there are no other issues.

I tried two different setups in the VB GUI for Host Audio Driver: PulseAudio and ALSA. I have attached the audio debugging logs for both cases.

Audio output is working fine and I didn't test it while debugging so all the *.wav files have no content.

Guest is Win10, audio out works ok (bit choppy at times on headphones).
Main issue is that Win10 does not see a mic device presented.

Connecting a USB sound device from Sennheiser to the host & then passing that through to the guest results in sennheiser audio out & new mic device presented, both of which appear ok (not much testing done beyond testing in the device settings).
Proves audio in/out presented to guest via USB devices is ok.
For native host audio, it would seem that the driver passthrough doesn't present the mic device correctly as an Intel HDA, so windows doesn't try to load/use it.

Attached the logfile VBox_Win10_Guest_Ubuntu_18.04_Host.log.gz

I also tried (briefly) use of Alsa (laggy) & ICH9/Realtek [win10 couldn't identify the hw properly] so reverted back to default (recommended) Pulse/intel HDA.