Version 32 (modified by Ramshankar Venkataraman, 13 years ago) ( diff )


Solaris build instructions

The Solaris port of VirtualBox is work in progress and so is this page. The current page is just an edited version of the GNU/Linux one.


You need:

  • Solaris Nevada build 70 and Solaris Developer Express 07/09 are the oldest versions VirtualBox can be expected to build on. Build 75 or later is strongly recommended.
  • GCC 3.4.3+. It will probably work with 3.4.6 or even 4.x.y, but 3.4.3 is the one we've tried and which problems we have worked around.
  • libxalan (only VBox version < 1.6, Xalan XSL library, depends on Xerces; again, the C++, not the Java version). You'll probably have to build this yourself or see check 1.
    The source:
  • libxml2 (only VBox version >= 1.6, XML file handling)
  • libxslt1 (only VBox version >= 1.6, XML file transformation)
  • Qt 3.3.x (with x >= 5 if possible; only for VBox version <= 2.2.0). You'll have to build this yourself.
    The source:

    Make sure QTDIR environment variable is pointing to the Qt installation and that the shared libraries can be found.
    Configure example (not the -I options for odd include locations):
    ./configure -v -platform solaris-g++-64 -thread -shared -stl -largefile -tablet -sm -disable-sql \
        -qt-imgfmt-jpeg -qt-imgfmt-png -qt-imgfmt-mng -qt-libjpeg -qt-libpng -qt-libmng -qt-zlib \
        -prefix /opt/vboxose-qt \
        -I/usr/include \
        -I/usr/X11/include \
        -I/usr/X11/share/include \
  • Qt 4.x.y (with x >= 4 if possible)
  • The PATH has to include the following directories:
    • /usr/sfw/bin - for gcc and related tools.
    • /usr/ccs/bin - for ar and other tools.
    • /usr/local/teTeX/bin/i386-pc-solaris2.10 - TeTex, internal only2.
  • The LD_LIBRARY_PATH has to include the following directories:
    • /usr/sfw/lib - for gcc and related tools.
    • /usr/ccs/lib - for ar and other tools.

1 The xerces and xalan sources we use together with the appropriate kBuild makefiles can be found here:
Untar them into the VirtualBox trunk directory and add --build-xalan as argument to configure whenever running it.

2 Items marked "internal only" is intended for VirtualBox team members only.

Building VirtualBox

  1. Change to the root directory of the sources and execute the configure script: ./configure --disable-hardening. If it finds everything it needs, it will create a file called 'AutoConfig.kmk' containing paths to the various tools on your system. Also, it will create an environment setup script called This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten).
  1. Whenever you want to build VirtualBox, you have to open a shell and source the generated environment setup script '', i.e. do
    source ./
  1. To build a release package, type kmk all. This produces the required binaries in out/solaris.x86/release/bin/. (If you want to build a debug version, type kmk BUILD_TYPE=debug.) In case you have more than one CPU core, you could take advantage of our parallel build system by supplying -j3 (number of cores + 1) as an option to kmk.

Running your build

You can run VirtualBox directly from the build target directory (out/solaris.x86/release/bin/). But first of all, you must install the VirtualBox kernel module. There is a script src/VBox/HostDrivers/Support/solaris/ which does this for you. It requires you to either install sudo or run it as root.

cd out/solaris.amd64/release/bin

For the other drivers you will need to copy the driver file and .conf file if any into the appropriate locations. Current drivers include vboxflt (bridged networking, host-only networking), vboxnet (host-only networking), vboxusbmon, vboxusb (USB drivers).

/platform/i86pc/kernel/drv/       (32-bit drivers and .conf files)
/platform/i86pc/kernel/drv/amd64  (64-bit drivers)

And then run as root/sudo: --setupdrivers

Finally, you can start one of the frontends, e.g.

Note: See TracWiki for help on using the wiki.

© 2023 Oracle
ContactPrivacy policyTerms of Use