These notes pertain specifically to OpenSolaris build 105 and VMWare Fusion v.2.01 on MacOS Leopard 10.5.6 ~ The host machine is a 13″ macbook with 2GB ram.


When initially creating a new virtual machine for Solaris 10 the default memory size is set to 580Mb.   At  this setting the install  either hangs or progresses so slowly that it might as well be hanged.  Increasing the memory to 1024Mb solves this problem and the install progresses and enters the graphical (X-windows) install for OpenSolaris.

Getting past the memory issue, the install continues but eventually fails due to lack of disk space.  The failure does not show up until  all questions have been answered from within the graphical install portion and the installer attempts to partition the provided disk space.  The default hard drive size is set to 8GB.  Setting this to 12GB does not prevent the failure of the installation.  Pre-allocating the disk space as a single file (not broken into 2GB chunks) was also ineffective; the installation still failed due to lack of disk space.  The install fails and the diagnostics appear to show that there was little to no disk space available.  This can be circumvented by manually partitioning the disk space.

Once the install process has reached the graphical portion, I was able to open a new terminal window and used the ‘fdisk’ command to create a new disk label (using solaris defaults) for the disk space provided within VMWare.  Once the disk was labeled and written, the install procedure was able to identify the disk space correctly and the install continued to completion.