Ticket #15660 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

SB16 audio selection crashes VMs

Reported by: socratis Owned by:
Component: audio Version: VirtualBox 5.1.2
Keywords: Cc:
Guest type: all Host type: Mac OS X


This is most probably the same as #15659, but it is worse in the fact that you simply don't get a warning (with the option to never show it again), this time the VM aborts.

Attaching logs from a NT4 guest, with and without aborting (

Attachments Download (44.7 KB) - added by socratis 7 years ago.
Windows NT4.vbox Download (19.2 KB) - added by socratis 7 years ago.

Change History

Changed 7 years ago by socratis

comment:1 Changed 7 years ago by frank

Hi Socratis, can you provde a core dump? You might want to contact me via PM.

comment:2 Changed 7 years ago by socratis

According to the wiki page, for an OSX host:

The core files can be found in the /cores folder.

No they can't. There's nothing there:

SGK-MBP2300:~ socratis$ ls -alR /cores/
total 0
drwxrwxr-t@  2 root  admin    68 25 Αυγ  2013 .
drwxr-xr-x  36 root  wheel  1292 20 Μαϊ 18:14 ..
SGK-MBP2300:~ socratis$

Permissions were compared and found to be the same as in a (mostly) unused 10.9 VM that I have (for cases like that). The only thing that I get when I start from the command-line is:

SGK-MBP2300:~ socratis$ /Applications/ -startvm "Windows NT4"
Segmentation fault: 11
SGK-MBP2300:~ socratis$

The solution can be found in where they state:

The /cores must be writable by the program that's dumping core. By default, it is only writable by root and by users in the admin group. If you need normal users to be able to dump a core, you can make the directory world writable with the command:

$ sudo chmod o+w /cores

That did it. You might want to update the wiki.

Now, how exactly do you want me to handle 876.597.248 bytes? Do you have a public site that I can upload the whole thing? Because I highly doubt that e-mail can handle 835 MiB in one go.

Edit: If you don't want to publicly tell me how, you can always PM me.

Last edited 7 years ago by socratis (previous) (diff)

comment:3 Changed 7 years ago by frank

Thanks for the hint, I've updated the wiki page. And sent you a PM.

comment:4 Changed 7 years ago by socratis

That PM that Frank sent me resulted in a couple more PMs back and forth. I'll post the gist of it and continue the discussion here.

Socratis : The link of the file is: (, 167.406 MB). The file will be available on the server for the next 7 days.

Frank : How did you create the core dump: Did the VM process crash as you wrote with the SB16 emulation? The core dump does not look like it was a crash...

Socratis : Yes, exactly. I mean, I didn't even touch the VM configuration. NT4 starts. I get the OS Loader options for safe mode, with a timeout. After that the blue screen where you see the CPU/RAM information. Right when it's about to switch to the high res graphics mode ... kaboom. VM disappears. I'll attach the VM.vbox to the ticket.

Frank : Maybe I understood you wrong: I thought your VM crashes if you are using SB16 but apparently that's not the case...

Resuming our normal operation...

Frank, to summarize, the VM crashes only if I use the "SB16" controller. If the host driver is "Null" or the controller is set to "Intel HDA" or "AC97" there is no crash. Simply the warning of ticket #15659.

Attaching the "Windows NT4.vbox".

Last edited 7 years ago by socratis (previous) (diff)

Changed 7 years ago by socratis

comment:5 Changed 7 years ago by socratis

I should have mentioned explicitly that the crash happens with ALL the VMs that use the SB16.

comment:6 Changed 7 years ago by frank

Back to this report: socratis, so your VM definitely crashes if you set the sound to SB16, is that correct? Did you test this with the most recent 5.1 test build or is this blocked by #15659 as well?

comment:7 Changed 7 years ago by socratis

I don't even have a chance to test whether there is sound or not, so, no it's not "blocked" by #15659. I'm not saying it's not the same source for the error, I'm saying I can't test it. Crash happens at the early stages of the guest booting. Version 5.1.3 build 109780 (Qt5.5.1).

comment:8 Changed 7 years ago by socratis

I think that in the latest test build 110033 you've successfully managed to merge #15659 and #15660. You now get both a warning and a crash on all the VMs, independent of the controller used.

:D (where are the emoticons when you really need them?)

comment:9 Changed 7 years ago by socratis

Hallelujah!!! YES!!!

This seems to be fixed with 5.1.4, although there was no mention in the release notes! It works for me, OSX 10.9.5 host. Can anyone verify/confirm this please?

PS. Regarding comment:8, you managed to merge #15659 and #15660, but you managed to fix them both at the same time in less than 3 days! Two birds with one stone! Excellent!!!

comment:10 Changed 7 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

I will close this ticket. Please reopen if still relevant with 5.1.4.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use