it looks like the are not willing to maintain this (at least for Solaris) because this thing is in a miserable >condition, e.g. missing files, make files not properly working, and so on.

I managed to get Virtualbox 3.1.2 OSE to compile a while back, but only when booting Nexenta in 32-bit mode by removing the $ISADIR part in grub's menu.lst. When you are booting in normal 64-bit mode, you also seem to need 64-bit libraries, which are not available for everything in Nexenta.

If you want to have a go at it. I believe the following was necessary:

• apt-get install sunwaudh libssl-dev
• compile curl, libidl, glib, libpng, gsoap from source or search for package.

• in Config.kmk:

• remove/comment out: VBOXWITHXPCOMNAMESPACECLEANUP = 1

• remove/comment out: VBOXWITHUSB = 1

• remove the Solaris specific part (as gcc doesn't support it) in: TEMPLATEVBOXR0DRVCFLAGS.amd64 = -m64 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow $(if $(VBOXSOLARIS10),,-msave-args) -mno-red-zone -mcmodel=kernel

• grab missing vboxfs* files from Virtualbox SVN.

Hi,

I did not say I was not able to to get this thing building. I just complaining about the miserable condition. I have now implemeted the neccessary setup in config and make files to build it out of the box on NexentaOS. This was neccessary to get the right VBoxPython libraries. Just 32 bit, but more is not required for NexentaOS.

As you could see in my post it is not neccessary to use the OSE version, because there is a much easier way using the original Solaris package and patch it. Only the VBoxPython libraries was not working on NexenatOS.

Ernst

As you could see in my post it is not neccessary to use the OSE version

For you as a private individual, it may not matter. But I have a small company, and using the OSE saves me from paying a license fee.

From the Virtualbox site:

This license applies if you download the full VirtualBox binaries from the Downloads page. It does not apply to the VirtualBox Open Source Edition (OSE), which falls under the GPL instead; see Editions for details about the differences between these releases.

In summary, the VirtualBox PUEL allows you to use VirtualBox free of charge

• for personal use or, alternatively,
• for product evaluation.
• In addition, academic use of VirtualBox is also permitted free of charge by the PUEL.

If you do not belong to either category, you will have to purchase a commercial license. Do not >hesitate to contact Sun Microsystems, Inc. in this matter.

Hi.

O.K. thats clear.

If you need, I have a patch and a description how to fix VirtualBox 3.1.4 OSE. It's just compiled for headless with 32 bits. I did not install it. It's not running with Qt4, because the version requiered by VirtualBox is not available from Nexenta. There is also a problem compiling webservice with SOAP (a g++ command problem I guess).

Ernst

When doing this step on NCP3a5:

myers@gir:~/virtualbox$ alien -d -s -c --reloc_root=/ VirtualBox-3.1.4-SunOS-r57640.pkg

I got these errors:

Warning: alien is not running as root!
Warning: Ownerships of files in the generated packages will probably be wrong.
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
822-date: warning: This program is deprecated. Please use 'date -R' instead.
822-date: warning: This program is deprecated. Please use 'date -R' instead.
Directory sunwvbox-1.0 prepared.

If I run as root the I get even more errors:

myers@gir:~/virtualbox$ sudo alien -d -s -c --reloc_root=/ VirtualBox-3.1.4-SunOS-r57640.pkg
Use of uninitialized value in chdir at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 412.
Use of chdir('') or chdir(undef) as chdir() is deprecated at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 412.
ln: accessing `VBoxHeadless': No such file or directory
Use of uninitialized value in chdir at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 416.
Use of chdir('') or chdir(undef) as chdir() is deprecated at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 416.
ln: accessing `VBoxHeadless': No such file or directory
Use of uninitialized value in chdir at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 417.
Use of chdir('') or chdir(undef) as chdir() is deprecated at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 417.
ln: accessing `VBoxHeadless': No such file or directory
Use of uninitialized value in chdir at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 422.
Use of chdir('') or chdir(undef) as chdir() is deprecated at /usr/share/perl5/Alien/Package/Pkg.pm line 629, <FILELIST> line 422.

I went with the non root version. But when I did this

myers@gir:~/virtualbox/sunwvbox-1.0$ sudo ./debian/rules binary

It produces a lot of output as the directions says, but it does error out:

dpkg-shlibdeps: warning: debian/sunwvbox/opt/VirtualBox/i386/VBoxSharedClipboard.so shouldn't be linked with VBoxREM.so (it uses none of its symbols).
dpkg-shlibdeps: warning: debian/sunwvbox/opt/VirtualBox/i386/VBoxSharedClipboard.so shouldn't be linked with libsocket.so.1 (it uses none of its symbols).dpkg-shlibdeps: warning: debian/sunwvbox/opt/VirtualBox/i386/VBoxSharedClipboard.so shouldn't be linked with libstdc++.so.6 (it uses none of its symbols).
dpkg-shlibdeps: failure: couldn't find library libz.so.1 needed by debian/sunwvbox/opt/VirtualBox/amd64/libQt3SupportVBox.so.4 (its RPATH is '/opt/VirtualBox/amd64:/usr/sfw/lib/amd64:/usr/sfw/lib:/usr/sfw/lib').Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH.
dh_shlibdeps: command returned error code 512
make: *** [binary-arch] Error 1

Hi,

Only the first line 'Warning: alien is not running as root!' is importent everything else is pretty normal and just warnings. You could simple ignore (I got the same) them. Please try first to login is root (no sudo) and execute afterwards all the steps I have mentioned in my description.

Ernst

Hi,

I overlooked your error report about libz.so.1: This is a bug in alpha 5 (#77). For now you must manually install the library with 'apt-get install lib64z1'.

Ernst

Ernst Gill wrote:

Please try first to login is root (no sudo) and execute afterwards all the steps I have mentioned in my description.

root@gir:~/virtualbox# ls
ReadMe.txt  VirtualBox-3.1.4-57640-SunOS.tar.gz  autoresponse     python-lib.tar.bz2   sunwvbox-1.0-20100217.diff.gz
VBox.zip    VirtualBox-3.1.4-SunOS-r57640.pkg    libz-64.tar.bz2  solaris-lib.tar.bz2  vbox-build.txt
root@gir:~/virtualbox# alien -d -s -c --reloc_root=/ VirtualBox-3.1.4-SunOS-r57640.pkg
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
sh: line 0: cd: sunwvbox-1.0/usr/bin: No such file or directory
822-date: warning: This program is deprecated. Please use 'date -R' instead.
822-date: warning: This program is deprecated. Please use 'date -R' instead.
Directory sunwvbox-1.0 prepared.
root@gir:~/virtualbox# ls -l
total 283100
-rw-r--r-- 1 root root      1886 Feb 27 01:37 ReadMe.txt
-rw-r--r-- 1 root root   2615197 Feb 27 01:37 VBox.zip
lrwxrwxrwx 1 root root        28 Feb 27 02:16 VBoxHeadless -> ../../opt/VirtualBox/VBox.sh
lrwxrwxrwx 1 root root        28 Feb 27 02:16 VBoxManage -> ../../opt/VirtualBox/VBox.sh
lrwxrwxrwx 1 root root        28 Feb 27 02:16 VBoxQtconfig -> ../../opt/VirtualBox/VBox.sh
lrwxrwxrwx 1 root root        28 Feb 27 02:16 VBoxSDL -> ../../opt/VirtualBox/VBox.sh
lrwxrwxrwx 1 root root        28 Feb 27 02:16 VirtualBox -> ../../opt/VirtualBox/VBox.sh
-rw-r--r-- 1 root root  81446135 Feb 27 01:37 VirtualBox-3.1.4-57640-SunOS.tar.gz
-rw-r--r-- 1 root root 202810880 Feb 27 01:37 VirtualBox-3.1.4-SunOS-r57640.pkg
-rw-r--r-- 1 root root       151 Feb 27 01:37 autoresponse
-rw-r--r-- 1 root root     50214 Feb 27 01:37 libz-64.tar.bz2
-rw-r--r-- 1 root root     80902 Feb 27 01:37 python-lib.tar.bz2
-rw-r--r-- 1 root root   2482062 Feb 27 01:37 solaris-lib.tar.bz2
drwxr-xr-x 8 root root         8 Feb 27 02:16 sunwvbox-1.0
-rw-r--r-- 1 root root      1864 Feb 27 01:37 sunwvbox-1.0-20100217.diff.gz
-rw-r--r-- 1 root root      2187 Feb 27 01:37 vbox-build.txt
root@gir:~/virtualbox#

I don't think all those broken symlinks should be in this directory. Shouldn't they be somewhere in "sunwvbox-1.0". Also, the directions do not mention what to do with python-lib.tar.bz2 and solaris-lib.tar.bz2.

Thanks

Hi,

I know, but the are generated by alien. The symlinks and the libraries python-lib.tar.bz2 and solaris-lib.tar.bz2 are integrated in the debian package during the debian package make process by './debian/rules binary'. You have nothing todo, just to copy all the files in one directory, start the debian package make process and install the package. Thats all.

Ernst

Hi,

Please find attached an updated description how to build vbox 'bvox-build.txt' to clearify some steps.

Ernst

Ernst Gill wrote:

I know, but the are generated by alien. The symlinks and the libraries python-lib.tar.bz2 and solaris-lib.tar.bz2 are integrated in the debian package during the debian package make process by './debian/rules binary'. You have nothing todo, just to copy all the files in one directory, start the debian package make process and install the package. Thats all.

Ok. I've tried that.

./debian/rules binary

Ends with:

dpkg-shlibdeps: failure: couldn't find library libz.so.1 needed by debian/sunwvbox/opt/VirtualBox/amd64/libQt3SupportVBox.so.4 (its RPATH is '/opt/VirtualBox/amd64:/usr/sfw/lib/amd64:/usr/sfw/lib:/usr/sfw/lib').
Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH.
dh_shlibdeps: command returned error code 512
make: *** [binary-arch] Error 1

From the directions it seems with NCP3a5 I don't need to do anything with the libz-64.tar.bz2, but I tried it anyway. Bingo! That step seems like it's still needed (or perhaps a symlink to a file from the zlib1g package?).

Also I had to install "libpng12-0" as well.

Do you mind if I turn these directions into a wiki page?

I just wanted to add that I'm installing Ubuntu in a VirtualBox VM on my headless server right now, watching the action from a RDP viewer on my laptop. Seems to work great! Thanks for putting these directions together!

myers

Hi,

It seems you have overlooked my post about the a bug in alpha 5 (#77). For now you must manually install the library with 'apt-get install lib64z1'. You do not need my libz-64.tar.bz2 anymore. This bug is fixed by Nexenta, but the library is not automatically installed.

Ernst

Hi!

Ernst, thanks for the guide!

But there are some additional dependencies. Add them to your guide, pls.

apt-get install libsm6 libxmuu1 libxrender1 libxdmcp6 libpng12-0 libfreetype6  Libfontconfig1

Pavel.

Hi,

I working on the 3.1.6 integration, and I will update my guide during this work. But it will take 2 or 3 weeks (currently I'am a little bit busy).

Ernst

Floris Bos wrote:

As you could see in my post it is not neccessary to use the OSE version

For you as a private individual, it may not matter. But I have a small company, and using the OSE saves me from paying a license fee.

From the Virtualbox site:

This license applies if you download the full VirtualBox binaries from the Downloads page. It does not apply to the VirtualBox Open Source Edition (OSE), which falls under the GPL instead; see Editions for details about the differences between these releases.

In summary, the VirtualBox PUEL allows you to use VirtualBox free of charge

• for personal use or, alternatively,
• for product evaluation.
• In addition, academic use of VirtualBox is also permitted free of charge by the PUEL.

If you do not belong to either category, you will have to purchase a commercial license. Do not >hesitate to contact Sun Microsystems, Inc. in this matter.

From the FAQ[1]:

Personal use is when you install the product on one or more PCs yourself and you make use of it (or even your friend, sister and grandmother). It doesn't matter whether you just use it for fun or run your multi-million euro business with it. Also, if you install it on your work PC at some large company, this is still personal use. However, if you are an administrator and want to deploy it to the 500 desktops in your company, this would no longer qualify as personal use. Well, you could ask each of your 500 employees to install VirtualBox but don't you think we deserve some money in this case? We'd even assist you with any issue you might have.

[1] http://www.virtualbox.org/wiki/Licensing_FAQ

Hi,

Here is the update for VirtualBox 3.1.6 and 3.1.8.

I have updated my description and new python libaraies for 3.1.6 and 3.1.8. Everything else is still working with the old files from my last update.

Ernst

Hi,

Sorry, I forgot.

Everything is working on Nexenta Core Platform 3.0 Beta 3 (I guess also on Beta 2, but I did not tested).

Ernst