Unable to start VM using GUI

[rjc]

After trying to start a VM (OpenBSD 5.6) using VirtualBox GUI, I get and error message:

Failed to open a session for the virtual machine openbsd. The virtual machine 'openbsd' has terminated unexpectedly during startup because of signal 6.

Details:

Result Code: NS_ERROR_FAILURE (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

The same VM starts just fine using command line:

vboxmanage startvm openbsd --type headless

Only reboot of the host fixes the issue. The host OS is OS X 10.9.5 but the problem occurred on earlier revisions of both, the OS and VirtualBox.

There's already one VM running (Windows 7), also in "headless" mode. AFAICR, it actually doesn't matter which one I try to start using GUI - as long as there's one already running, I seem to get this error.

[Kirkc]

Contents of the OS X system log when attempting a normal startup.

[Kirkc]

I run into the same issue. I am currently running VB 5.0.20 r106931 on OS X El Capitan 10.11.5 with several VMs (Ubuntu and FreeBSD). These are typically run headless, with no user logged-in to the host (OS X). Occasionally, when I log in to the host and try to connect to the VMs (i.e., clicking the "show" button in the VirtualBox Manager) there is a quick popup indicating an attempt to connect, but no VM window appears.

Additionally, if I shut down a VM and try to do a "normal" start, I get the error described above. For example:

The virtual machine 'TeamServer' has terminated unexpectedly during startup because of signal 6.

Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

There do not appear to be any additional entries to the vbox.log for the subject VM when attempting the normal start. However, messages do appear in the OS X system log. These are attached as console.log. I have also attached the crash report referenced in the console.log.

A headless start works fine.

The only way I have been able to clear this up is to reboot the host OS (OS X). This reliably clears up the issue, but it always returns at some point.

[Kirkc]

Crash report referenced in console.log.

[Frank Mehnert]

Please reopen if still relevant with VBox 5.1.22.

[RPires]

I have version 5.1.22 r115126 and I have the same problem. Thank you

[Frank Mehnert]

RPires, in that case I would like to have some more information. Absolute minimum is the VBox.log file of such a crashing VM session.

[Frank Mehnert]

No additional information required, closing.