Sound Not working

[ritik135]

I installed macOS Catalina guest on my windows 10 host.Everything works fine but the sound doesn't work.No input or output devices are available on guest OS.I tried all 3 audio controller options i.e intelhdaudio,soundblaster16, but nothing seems to work.

[socratis]

I tried all 3 audio controller options i.e intelhdaudio,soundblaster16, but nothing seems to work

Stick with the template defaults, i.e. "Intel HD Audio". Trying things at random won't work for sure.

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[ritik135]

I am trying IntelHDaudio only but it doesn't seem to work.macOS doesn't recognize the internal speakers or any headphones either.

[rpmurray]

Socratis, I think you missed this part

I installed macOS Catalina guest on my windows 10 host

[mpack]

Acer PC, not Apple.

Important notice regarding Mac OS X as Guest.

[socratis]

Socratis, I think you missed this part

I installed macOS Catalina guest on my windows 10 host

'rpmurray', no, I didn't miss that part at all...

Here's a log snippet for you, see if you can tell me what's this running on:

VirtualBox VM 5.2.4 r119785 win.amd64 (Dec 18 2017 15:47:18) release log
...
00:00:03.313670 OS Product: Windows 10
00:00:03.313671 OS Release: 10.0.15063
...
00:00:03.498667 DMI Product Name: MacBookPro11,5
...
00:00:03.502073 Package type: WINDOWS_64BITS_GENERIC
...
00:00:03.678164 Guest OS type: 'MacOS109_64'

Hint; it's a fruit...

[mpack]

I don't understand. What log is that a snippet from? Because it isn't the log that "ritik135" posted above!

00:00:03.185637 VirtualBox VM 6.0.12 r133076 win.amd64 (Sep 3 2019 10:36:06) release log
00:00:03.185643 Log opened 2019-10-09T11:46:15.301560500Z
00:00:03.185644 Build Type: release
00:00:03.185648 OS Product: Windows 10
00:00:03.185649 OS Release: 10.0.18362
00:00:03.185650 OS Service Pack:
00:00:03.281282 DMI Product Name: Predator PH315-51
00:00:03.286204 DMI Product Version: V1.19
00:00:03.286217 Host RAM: 8034MB (7.8GB) total, 4215MB (4.1GB) available
00:00:03.286226 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:03.286227 Process ID: 6824
00:00:03.286227 Package type: WINDOWS_64BITS_GENERIC
00:00:03.288105 Installed Extension Packs:
00:00:03.288141 Oracle VM VirtualBox Extension Pack (Version: 6.0.12 r133076; VRDE Module: VBoxVRDP)
00:00:03.289163 Console: Machine state changed to 'Starting'
00:00:03.289330 Qt version: 5.6.2
00:00:03.292522 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:03.381651 SUP: Loaded VMMR0.r0 (C:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:03.381675 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:03.381681 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xXXXXXXXXXXXXXXXX
00:00:03.384903 Guest OS type: 'MacOS_64'

[socratis]

I don't understand. What log is that a snippet from?

1. 'ritik135' asks the question, they refer to a "windows 10 host".
2. I ask for the log, log is posted.
3. 'rpmurray' asked why I asked for the log, since it was already a "windows 10 host", that must have been a Hackintosh.
4. I replied with a snippet from my log, where I'm running Win10 on a MBP. Just by running Win10 doesn't mean that you can't have a valid OSX guest, it's not proof enough.

[mpack]

Ah, I see. In fact I already understood that possibility, which is why I chose the first words of my first response. I guess I would have been less confused if you had said "my log" somewhere in your post.

[socratis]

I guess I would have been less confused if you had said "my log" somewhere in your post.

I didn't want to make it personal!