Sound doesn't work on VB 5.1.2

[thorhall]

[Mod. edit: Added summary and tickets]

---

The bug seems to be fixed with versions 5.1.4 and later.

There is a bug in versions between 5.1.0 and 5.1.2 (more fine grain between builds 108857 and 108931), where there is a warning and no sound in any of the guests, in OSX versions 10.9 through 10.11. The warning message is as follows:

The virtual machine execution may run into an error condition as described below. We suggest that you take an appropriate action to avert the error.

Details
Some AC'97 audio streams (PCM Output) could not be opened. Guest applications generating audio output or depending on audio input may hang. Make sure your host audio device is working properly. Check the logfile for error messages of the audio subsystem.

Error ID: HostAudioNotResponding
Severity: Warning

The bug is irrelevant of whether you use "AC'97", "HDA" or "SoundBlaster".

There are two tickets for this open for this. Add your comments there to be notified in case of a fix:
#15659: PCM missing warning on all VMs, independent of sound controller.
#15660: SB16 audio selection crashes VMs.

[Original post follows]

---

Hello all, can anyone help me or tell me if this is a bug in Virtualbox or OS X? I have windows 7 and windows 10 VMs and they both throw up the same error message attached. I'll send my vbox.log file as well if it provides any insight to my issue. Not having sound makes the VM partly unusable.

[thorhall]

here is my vbox.log

[tkvb]

I also get this error when I try to start a CentOS VM that worked fine before 5.1.x

[AALLeeXX]

Same here running Ubuntu on ElCapitaim, AC'97 errors just appeared in latest 5.2 that was not present in 5.1.
Extensions and guest additions updated as necessary made no change.

[socratis]

It was first discussed in Discuss the 5.1.2 release. I've already open two tickets for this:
#15659: PCM missing warning on all VMs, independent of sound controller.
#15660: SB16 audio selection crashes VMs.

Feel free to add your experience to the appropriate ticket. Again, to clarify, you always get a warning, but if you use the SoundBlaster you get a warning AND a VM crash. If you could test the 2nd one it would be great, since I'm the only one seeing it at the moment. I think...

[MelRay]

I too experienced the same after upgrading the the latest. I have not experienced the crash but along with the other reports already here this is my experience. OS X 10.11.6. I have never had an issue with any vm whether Windows or Linux prior to this latest release.

[loukingjr]

Oh boy. Host: OSX 10.11.6 - VB 5.1.2
No audio…
1. Windows 10 guest Intel HD Audio controller
2. Ubuntu 16.04.1 LTS guest. ICH AC97 Controller.

Edit: I don't get any warnings or error messages.

[Mr. Tee]

Same problem here... think it came with the Mac Os upgrade since the Virtualbox 5.1 beta worked fine for me (before the Mac Os upgrade to 10.11.6)

[dbjungle]

I have this problem on a Windows 10 host on VirtualBox v5.1.2 with Windows guests also. I don't get the warning, sound just stops working.

[Andy Silva]

Also happening in Yosemite 10.10.5 and VirtualBox 5.1.2, in Windows Server 2003 guests and a Windows Server 2008 guest. Changing the Host Audio Driver to null gets rid of the error and allows the guest to boot, but (obviously) without sound. I'd like my sound back, please.

[MrDenver]

I experience no sound when I minimize the guest (windows 10) and the return to the guest machine. The only way I get it back is to restart the guest.

Thanks

[michaln]

I have this problem on a Windows 10 host on VirtualBox v5.1.2 with Windows guests also. I don't get the warning, sound just stops working.

If you have any kind of problem on hosts other than OS X, please do not post in the OS X forum section because you will be ignored.

[grayfox]

I have the same problem on my late 2011 macbook pro running the very latest mac (10.11.6) and xbox (5.1.2) software.

My vm is Fedora 24 (32 bit) with last update made on 7/25/2016

[socratis]

the very latest mac and vbox software

Please be more precise. Exact versions. When someone is reading your post in three months "the latest" will not be the same and your problem might not apply.

[Benjamin1974]

I have the same problem since upgrading VB to 5.1.2.

Here's how it goes with me:

Host - Macbook Pro i7 16GB RAM 1GB SSD Late 2013 running El Capitan 10.11.6

Guests - Windows 10, Windows 7 Pro and Win XP. (all running the latest MS updates, but the issue was there before I updated any of the Guest OS's)

Prior to upgrading yesterday I was running VB 5.0.24 with no problems.

When I start any of the VMs I get the warning message the OM posted. That's fine. It's just a warning/advice so I'll bear it in mind but it doesn't mean anything is going to blow up.

However, each of the Windows guests are exhibiting the same problem - namely that there is no sound output on the host. As far as Windows is concerned the sound "card" is working. At this point I have to say it DOES NOT MATTER if I use Intel HD Audio, AC97 or SoundBlaster flavours - they all exhibit the same fault (and I don't get any crashes or BSODs)

If I use Windows Device Manager to look at the "hardware" it can see the VB soundcard fine. No issues there. In fact I can play a file, music, etc or even load YouTube and play something. The Windows level meters in Control Panel > Sound dance away merrily showing me a level. So all my Windows think the world is dandy.

But, however, nothing comes out of the Host. Using the Mac volume keys produces Mac noises so it's not the Mac. And yet the Windows level meters show a level and the Device Manager is happy. It just seems to be the virtual pipe between the Guest Windows and the Host Mac that's broken with this update.

I hope that's enough info and it's crystal what my issue/experience is.

Many thanks,

Benjamin.