Ticket #4468 (closed defect: fixed)

Opened 9 years ago

Last modified 9 years ago

VirtualBox 3.0.0 fails to start in OpenSolaris non-global zone

Reported by: gpatrick Owned by:
Priority: major Component: other
Version: VirtualBox 3.0.0 Keywords:
Cc: Guest type: other
Host type: Solaris


Failed to initialize COM or to find the VirtualBox COM server. Most likely, the VirtualBox server is not running or failed to start.

The application will now terminate.

Details: Callee RC: NS_ERROR_FAILURE (0x80004005)

2.2.0 works in a non-global zone, however, later releases constantly fail. I WANT to run OpenBSD in VirtualBox but OpenBSD gets seg faults and disk full errors in earlier releases of VB. Although I heard OpenBSD runs on VirtualBox 2.2.4 this doesn't work because I need to run VirtualBox in a non-global zone and that means I can only use 2.2.0 and OpenBSD gets seg faults and disk full errors and doesn't run and OpenBSD only works on 2.2.4 which doesn't work in a non-global zone.

Why doesn't anyone fix the current problems before creating a newer release which doesn't address any prior issues?

Change History

comment:1 Changed 9 years ago by gpatrick

Was successful with VBox 3.0.2 in a non-global zone with a FreeBSD 7.2 guest. OpenBSD 4.5 guests still get disk full and segmentation faults on installation and seg faults on startup and shutdown.

comment:2 Changed 9 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use