virtualbox.org

The Guest Control File Manager works fine on guests running Solaris 11.4 as reported before.

The VBoxSolarisAdditions.pkg package also still installs fine on Solaris 10 u10

So the Guest Control File Manager (which *depends* on the guest additions as far as I understand) also works on Solaris 10 guests running VBoxService ...

The 6.0.0beta3 guest additions install fine on Solaris10, also the vboxfs filesystem works.

There is one remark: a "minimal" Solaris install has no OpenGL or libgcc_so.1 so the guest additions warn that it can't install the OpenGL driver (logical but not very nice as it doesn't check this condition very well).

# cat /etc/release
                    Oracle Solaris 10 8/11 s10x_u10wos_17b X86
  Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
                            Assembled 23 August 2011
# svcs -a | grep vbox
maintenance    10:51:02 svc:/application/virtualbox/vboxservice:default
maintenance    10:51:02 svc:/application/virtualbox/vboxmslnk:default
# modinfo | grep vbox       
166 fffffffff7f85000  30fc8 231   1  vboxguest (VirtualBox GstDrv 6.0.0_BETA3r1)

207 fffffffff81ab000   4870 232   1  vboxms (VBoxMouseIntegr 6.0.0_BETA3r127)
# /usr/bin/VBoxService
ld.so.1: VBoxService: fatal: libgcc_s.so.1: open failed: No such file or directory

when doing a full Solaris install this is not an issue as both libgcc_s.so.1 and OpenGL are installed.

# ldd /usr/bin/VBoxService
        libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1
        libc.so.1 =>     /lib/libc.so.1
        libm.so.2 =>     /lib/libm.so.2

as soon as the /usr/sfw is present, the VBoxService starts up fine, and the Guest Control File Manager works as well on Solaris 10

# ps -ef | grep VBox
    root   765   668   0 11:44:26 ?       0:00 /opt/VirtualBoxAdditions/amd64/VBoxService guestsession --session-id=1 --sessio
    root   668     1   0 11:43:31 ?       0:00 /usr/bin/VBoxService
    root   779   777   0 11:45:35 pts/1   0:00 grep VBox

Nice to hear that the file manager works on Solaris 10. And yes file manager work on guest control system which requires GAs.

Although it works fine, just a remark , if you look at the ps -ef output, it can be seen that the ELF-32 bit executable is ran /usr/bin/VBoxService.

The manifest file from /var/svc/manifest/application/virtualbox (for Solaris 10) starts the ELF-32 bit /usr/bin/VBoxService.

Then later when using the Guest Control File Manager it can be seen in the ps -ef output that the /opt/.../amd64/VBoxService is launched that is the ELF-64 bit executable which has (logically) different dependencies for shared libraries.

This is related to the complex and subtle issue of the SMF manifest, perhaps it could be changed to run the amd64 ELF-64bit service to start with.

But because there may be more important issues, just to mention that the new functionality for "File Manager" and GA still works on sol10 ...

No change is required on the SMF manifest file at least not regarding /usr/bin/VBoxService.

When ran on Solaris 10 u10 32bit bit, the SMF service correctly starts the 32bit versions:

# ps -ef | grep VBox
    root   435     1   0 08:52:42 ?           0:00 /usr/bin/VBoxService
    stes   945   435   0 08:54:39 ?           0:00 /opt/VirtualBoxAdditions/i386/VBoxService guestsession --session-id=1 --session

so in the 64bit case the ELF64 (amd64 subdirectory) VBoxService is launched for the "guestsession",
and in the 32bit case the i386 subdirectory is correctly used by VirtualBox.