VirtualBox 4.1.6 fails to load on Solaris 11 release

[palowoda]

I've done a clean install of Solaris 11 and Virtualbox 4.1.6.
The program starts up and than gives me an error box with the following text:

Callee RC: NS_ERROR_CALL_FAILED (0x800706BE

In my log file I have:

VirtualBox (XP)COM Server 4.1.6 r74713 solaris.amd64 (Nov 4 2011 12:44:25) release log
00:00:00.000 main Log opened 2011-11-17T07:39:32.410860000Z
00:00:00.000 main OS Product: SunOS
00:00:00.001 main OS Release: 5.11
00:00:00.001 main OS Version: 11.0
00:00:00.001 main OS Service Pack: 11.0
00:00:00.001 main Executable: /opt/VirtualBox/amd64/VBoxSVC
00:00:00.001 main Process ID: 4107
00:00:00.001 main Package type: SOLARIS_64BITS_GENERIC
00:00:00.113 nspr-2 Loading settings file "/home/palowoda/.VirtualBox/VirtualBox.xml" with version "1.7-solaris"
00:00:00.115 nspr-2 USBLibR3:RTFileOpen failed to open VBoxUSB device.rc=-38
00:00:00.217 nspr-2 VDInit finished
00:00:00.220 nspr-2 Loading settings file
blah, blah loads all the virtual machines correct.
Than dies.


What is this USBLibR3:RTFileOpen failed to open VBoxUSB device.rc=-38 some sort of missing file or a file with an incorrect permission?

---Bob

[palowoda]

Actually to add detail of the box error it said:
Failed to determine the accessibility state of the medium
Callee RC:
NS_ERROR_CALL_FAILED (0x800706BE)

I'm not sure if its related to the logged error about the usb devices.
Additional information. This box ran fine with Vbox 4.1.6 and opensolaris 134.
All that I did was add a new drive, install Solaris 11 and a new Vbox 4.1.6 and
I'm using my old VM's from the imported home directory pool.

---Bob

[guyverdh]

I presume the following (as I've got 4.1.6 running under Solaris 11 11/11)

The userid you're logged in with is in the vboxuser group.
After installing, you installed the VirtualBox extensions pack that enables the virtual usb interfaces.

When you did your fresh load of the OS, did you use the live-cd/dvd and run the hardware scan tool?

I noticed that there were some drivers removed and older hardware support removed in the official release (/dev/ce to name the one that impacted me on a workstation I'd put together).

[palowoda]

Problem solved
--- In solarisx86@yahoogroups.com, "rwager1" <rick@...> wrote:
>
>
> I see something similar on open indiana
>
> Resolved by adding this to /usr/bin/VirtualBox
>
> LD_NODIRECT=1
> export LD_NODIRECT
>
> Perhaps it'll help you out, also.
>

Ah hah. You are right. In fact I should have realized this from the beginning
because it happened to me on an OpenIndiana install. What got me is that I
loaded the gcc 4.6 from the openindiana sfe repo and that is where the problem
originates. In any case I dropped back to the Oracle 4.5 gcc and VirtualBox is
happy now. I really want to understand why LD_NODIRECT is needed and if would
affect any other applications.

So this only affected me and openindiana users.

---Bob