Error -1912: Can't start headless VM

[bewst]

I'm getting this with 3.1.4:

Code: Select all

# VBoxHeadless --startvm WinInstallerBuilder
VBoxHeadless: Error -1912 in supR3HardenedMainInitRuntime!
VBoxHeadless: RTR3Init failed with rc=-1912

VBoxHeadless: Tip! It may help to reinstall VirtualBox.
# VBoxManage startvm WinInstallerBuilder --type vrdp
Sun VirtualBox Command Line Management Interface Version 3.1.4
(C) 2005-2010 Sun Microsystems, Inc.
All rights reserved.

Waiting for the remote session to open...
ERROR: Virtual machine 'WinInstallerBuilder' has terminated unexpectedly during startup
Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee <NULL>

IIUC, VirtualBox 3.1.x are not compatible with the latest official release of OpenSolaris, 2009.06, because it is based on build 111 of Nevada rather than build 124+

Is that correct, and is it the cause of the problem I'm seeing?

Which is the latest version of VirtualBox I can roll back to that will work on the OSOL release, please?
Shouldn't this version be prominently linked on the downloads page?
Shouldn't more recent releases have a giant warning on them if I must install a developer snapshot of the OS to use them?

Thanks,
Dave

[bewst]

Ugh, this is bad. I downgraded to 3.0.12r54655, which is supposed to work with my build of OSOL, and I am still getting the same problem. I even get this error from “VBoxHeadless --help”! What am I doing wrong?

[Perryg]

I think it is something else. From the manual 3.1.4

Solaris hosts (32-bit and 64-bit[4]) are supported with the restrictions listed in Chapter 13, Known limitations:
OpenSolaris (2008.05 and higher, "Nevada" build 86 and higher)
Solaris 10 (u5 and higher)

The known limitations are:

Solaris hosts. For OpenSolaris and Solaris 10 U5/U6, the following restrictions apply:
There is no support for USB on Solaris 10 hosts.
Experimental USB support for OpenSolaris/Nevada hosts (versions 124 and higher recommended).
No ACPI information (battery status, power source) is reported to the guest.
No support for using wireless with bridged networking.

What you need to figure out is what changed between the time it was working until the time it stopped working. What changed?

[bewst]

I don't think anything significant changed other than that I installed the VBox update. Any ideas on how I could find out what might have changed in more detail? VBox is running in a non-global zone, for what that's worth.

[Perryg]

So is WinInstallerBuilder the Win 2K or what?
You may need to wait for ramshanker to drop by of file a ticket with bugtracker. Since you did what the error massage said that would be your next step. I do not know what this error is myself. I have never seen it before.

[bewst]

Yes, WinInstallerBuilder is a Win2K server VM, why?
Is Win2K currently broken?

[Perryg]

That part I can not swear to. I do know they dropped support for Win2K at the end of version 1.6.X as host. It might be an issue but you would need to ask the DEVs about that.
Post to bugtracker and see what they have to say. bugtracker. You will need to setup an account there as it is on a different system.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

[bewst]

Oops. It's Windows 2003 server

[bewst]

Actually this clearly has nothing to do with the Guest OS:

# VBoxSDL --help
VBoxSDL: Error -1912 in supR3HardenedMainInitRuntime!
VBoxSDL: RTR3Init failed with rc=-1912

VBoxSDL: Tip! It may help to reinstall VirtualBox.

[bewst]

Bugtracker ticket: http://www.virtualbox.org/ticket/6337