Mac OS X 10.11.6 guest Mac OS X 10.10.5 host has Audio Problems.

[Lars Sonchocky-Helldorf]

The following dialog keeps showing up, regardless the settings:

Some HDA 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:

btw: same happend with windows 7 client. Warning []

[Lars Sonchocky-Helldorf]

screenshot

[mf]

duplicate of https://www.virtualbox.org/ticket/15668

[Lars Sonchocky-Helldorf]

You closed this ticket as a duplicate for https://www.virtualbox.org/ticket/15668 which is fixed now (sound works for Windows guests again) but you did not fix this for Mac OS X Server guests.

There are no audio devices available for Mac OS X Server 10.11 and OS X beta 10.12 guests on my Mac OS X 10.10 host running VirtualBox 5.1.4

[Lars Sonchocky-Helldorf]

No audio output devices available

[Lars Sonchocky-Helldorf]

no audio input devices available

[Lars Sonchocky-Helldorf]

VM settings general

[Lars Sonchocky-Helldorf]

VM settings audio

[Lars Sonchocky-Helldorf]

VirtualBox 5.1.4 is affected

[Socratis]

Replying to IOOI:

You closed this ticket as a duplicate for #15668 which is fixed now (sound works for Windows guests again) but you did not fix this for Mac OS X Server guests.

The bug itself was also a duplicate of #15659 which was also closed, correctly, with 5.1.4.

There are no audio devices available for Mac OS X Server 10.11 and OS X beta 10.12 guests on my Mac OS X 10.10 host running VirtualBox 5.1.4

This was an older bug (#15611) which was also fixed with 5.1.4. Are you sure you are running 5.1.4? Please post a VBox.log. ZIP it first.

PS. Next time, could you please downsize your attached images by 50% (at least). Not everyone is blessed with a HiDPI display. Plus you will be saving some (digital) trees ;)

[Lars Sonchocky-Helldorf]

Replying to socratis:

Replying to IOOI:

You closed this ticket as a duplicate for #15668 which is fixed now (sound works for Windows guests again) but you did not fix this for Mac OS X Server guests.

The bug itself was also a duplicate of #15659 which was also closed, correctly, with 5.1.4.

There are no audio devices available for Mac OS X Server 10.11 and OS X beta 10.12 guests on my Mac OS X 10.10 host running VirtualBox 5.1.4

This was an older bug (#15611) which was also fixed with 5.1.4. Are you sure you are running 5.1.4?

I am pretty sure. This is copied from the about box:

Version 5.1.4 r110228 (Qt5.5.1)

Please post a VBox.log. ZIP it first.

I will do so.

PS. Next time, could you please downsize your attached images by 50% (at least). Not everyone is blessed with a HiDPI display. Plus you will be saving some (digital) trees ;)

[Lars Sonchocky-Helldorf]

Vbox.log of 10.11 guest zipped

[Lars Sonchocky-Helldorf]

VBox.log of 10.12 guest zipped

[Lars Sonchocky-Helldorf]

Sound assertion in AppleHDAController at line 567 screenshot

[Socratis]

Please do not get confused. The sound assertion message is a normal one.

Can you please post the "<VM_Name>.vbox" for the 10.11 guest? I have a suspicion but I've got to make sure.

[Lars Sonchocky-Helldorf]

Mac OS X 10.11.vbox

[Lars Sonchocky-Helldorf]

Mac OS X 10.12.vbox

[Socratis]

Just as I thought!!! You followed an online tutorial, didn't you? And it smells a lot like this is a Hackintosh version. Here is what I consider as evidence:

• You have your hard drive set as VMDK. Nobody bypasses the defaults proposed, unless they read a (usually useless) blog post.
• You changed the chipset to PIIX3 from the default ICH9. Default OSX installations require ICH9, or they won't boot. Default Hackintosh installations require PIIX3, or they won't boot.
• You enabled a different CPU than you have. A hack (as in Hackintosh). By doing:

  <CpuIdLeaf id="1" eax="198313" ebx="133120" ecx="2147484161" edx="395049983"/>
  or else
  VBoxManage modifyvm <vmname> --cpuidset 00000001 000306a9 00020800 80000201 178bfbff
  

• You have two CD/DVDs attached: "ElCapitan_1.iso" and "ElCapitan_2.iso". OSX install media do not come in pairs. Where and how did you get these?

[Lars Sonchocky-Helldorf]

Are you suspecting me using a hackintosh? Sorry, this is ridiculous! I can prove not using a hackintosh by attaching a screenshot (if you trust this).

Replying to socratis:

Just as I thought!!! You followed an online tutorial, didn't you? And it smells a lot like this is a Hackintosh version. Here is what I consider as evidence:

• You have your hard drive set as VMDK. Nobody bypasses the defaults proposed, unless they read a (usually useless) blog post.
• You changed the chipset to PIIX3 from the default ICH9. Default OSX installations require ICH9, or they won't boot. Default Hackintosh installations require PIIX3, or they won't boot.
• You enabled a different CPU than you have. A hack (as in Hackintosh). By doing:

  <CpuIdLeaf id="1" eax="198313" ebx="133120" ecx="2147484161" edx="395049983"/>
  or else
  VBoxManage modifyvm <vmname> --cpuidset 00000001 000306a9 00020800 80000201 178bfbff
  

• You have two CD/DVDs attached: "ElCapitan_1.iso" and "ElCapitan_2.iso". OSX install media do not come in pairs. Where and how did you get these?

I created those using a shell script I found somewhere on the web.

[Lars Sonchocky-Helldorf]

My Desktop (exported as JPEG to get a smaller size)

[Lars Sonchocky-Helldorf]

Is this really a hackintosh?

[Socratis]

I didn't suggest that your host is a Hackintosh. I said that the evidence points to the guest being a Hackintosh. You do see the difference, right? Plus your desktop is not a proof that you're not trying to install a Hacintosh guest. I already saw the full details of your host from the logs. So, please stop attaching things that do not help particularly.

Now, you didn't post the link to the shell script that you found on the web, so I can't tell what they're doing, but I know one thing: chances are that they're wrong. On top of that shell scripts do not create VMDKs, change chipsets or modify the CPU, so there must have been a guide someplace. Please post a link to it as well.

[Lars Sonchocky-Helldorf]

Replying to socratis:

I didn't suggest that your host is a Hackintosh. I said that the evidence points to the guest being a Hackintosh. You do see the difference, right? Plus your desktop is not a proof that you're not trying to install a Hacintosh guest. I already saw the full details of your host from the logs. So, please stop attaching things that do not help particularly.

Now, you didn't post the link to the shell script that you found on the web, so I can't tell what they're doing, but I know one thing: chances are that they're wrong. On top of that shell scripts do not create VMDKs, change chipsets or modify the CPU, so there must have been a guide someplace. Please post a link to it as well.

I did the 10.11 installation quite some time ago, so I don't really remember, but it could have been this page:

​https://sandstorm.de/de/blog/osx-yosemite-in-virtual-box.html

, at least the script looks similar. I remember trying several different scripts to create a bootable ISO. Those scripts contain these links:

​http://forums.macrumors.com/threads/el-capitan-bootable-dvd.1923931/#post-22036604 ​http://forums.macrumors.com/threads/how-to-create-el-capitan-os-x-bootable-dvd.1923894/page-2#post-22048507 ​http://anadoxin.org/blog/creating-a-bootable-el-capitan-iso-image.html ​http://apple.stackexchange.com/a/211722/92486

what's wrong with those ways to create an ISO? How to install OS X in Vbox otherwise?

[Lars Sonchocky-Helldorf]

I switched the chipset to ICH9, now the sound output is working, I can hear the warning sounds for both 10.11 and 10.12 beta guests. Sound Input is visible, both microphone and line in inputs, but those are not working. The host has only a microphone, no line in however.

[Lars Sonchocky-Helldorf]

I can attach one screenshot of both the host sound input meter showing signal and the client one showing no signal the same moment.

[Socratis]

Replying to IOOI:

I can attach one screenshot of both the host sound input meter showing signal and the client one showing no signal the same moment.

NO! DON'T! We've had enough of screenshots already that did nothing to help us. If you could only use Google to search for something similar...

Oh, wait...

[Lars Sonchocky-Helldorf]

Replying to socratis:

Replying to IOOI:

I can attach one screenshot of both the host sound input meter showing signal and the client one showing no signal the same moment.

NO! DON'T! We've had enough of screenshots already that did nothing to help us. If you could only use Google to search for something similar...

Oh, wait...

Hi socratis,

I am interested to get that bug fixed in Vbox. What exactly I am supposed to do? Please elaborate …

regards!

[Socratis]

Aren't you the lucky one... I was about to point you to ticket #14386, but apparently the new test build released just today (>= 110346) fixes the problem. So download it and give it a try. It works so far with all the clients I've tested.

[Lars Sonchocky-Helldorf]

I am currently testing Version 5.1.5 r110346 (Qt5.5.1) and the sound input works somewhat now. Sometimes the interfaces (mouse pointer related stuff and / or sound input stops working) start to act strange, then it helps to freeze and unfreeze the machine (save the machine state). Then it starts working again. I can provide the log again if that is needed.

[Socratis]

I think that this is turning more to a back and forth discussion. May I suggest that we move this to the forums? That's where "discussions" are supposed to take place. Not in a bug report.

[Lars Sonchocky-Helldorf]

VBox.log on VBox Version 5.1.5 r110354 (Qt5.5.1) of 10.12 guest zipped

[Lars Sonchocky-Helldorf]

VBox.log on VBox Version 5.1.5 r110354 (Qt5.5.1) of 10.12 guest zipped subsequent run after awaking from sleep/freeze

[Lars Sonchocky-Helldorf]

Tests of VBox Version 5.1.5 r110354 (Qt5.5.1) with a 10.12 guest resulted in the attached Vbox.logs. Right after boot sound input was not working, it started working after a "safe the machine state" freeze and unfreeze. VBox.10.12.log.1 is from the boot till the freeze, VBox.10.12.log.

[Lars Sonchocky-Helldorf]

VBox Version 5.1.6 r110634 (Qt5.5.1) has working Audio (Microphone) Input only after putting a running macOS 10.12 beta guest VM to sleep (save machine state) and wake it up again. Right after booting the VM only Audio Output works.

[Lars Sonchocky-Helldorf]

This still happens with VirtualBox 5.1.8 r111374 (Qt5.5.1)

[aeichner]

No activity for over 3 years, please reopen if still an issue with a recent VirtualBox release (there were quite some audio fixes in the meantime).