software wanted: vmware player and/or virtualbox

[Arslan S.]

I gave a quick shot and successfully compiled vbox kernel modules for 64 bit tiny core kernel

first open up a toolchain64-shell through menu entry
or open up a standart terminal and run toolchain64-shell

prepare linux source before compiling modules

Code: [Select]

LINUX_SRC=$PWD/linux-2.6.33.3

[ -d linux-2.6.33.3 ] && sudo rm -rf linux-2.6.33.3

tar xf linux-2.6.33.3-patched.tbz2

cd linux-2.6.33.3

cp -f ../config-2.6.33.3-tinycore64 .config

make oldconfig CROSS_COMPILE=x86_64-unknown-linux-gnu-

make modules_prepare CROSS_COMPILE=x86_64-unknown-linux-gnu-

if [ ! -e /usr/src/linux ]; then
sudo mkdir -p /usr/src
sudo ln -s $LINUX_SRC /usr/src/linux
fi

if [ ! -e /lib/modules/2.6.33.3-tinycore64/build ]; then
sudo ln -s /usr/src/linux /lib/modules/2.6.33.3-tinycore64/build
fi
and then compiling modules from vbox src directory is as simple as

Code: [Select]

make CROSS_COMPILE=x86_64-unknown-linux-gnu-
tested on microcore64 3.0

[ricky]

Hallo Arslan S.,
if I followed your last advice and run the "make" command in toolchain64-shell, without loading compile.tcz, I received "make: command not found".
What was wrong ?

[Arslan S.]

of course you need to load compiletc just use toolchain64 instead of gcc to compile

[ricky]

Hurrah! Now I compiled the vbox kernel modules in 64 bit sucessfully. Thank you for help!
The next problem will be to include it in VirtualBox-3.2.6. But modprobe will be not enough. After a try I got already the message "modprobe is not supported" . But in terminal it worked with sudo.
So let's work and do some "trial and error".

[ricky]

VirtualBox-3.2.6-Linux_amd64.run wouldn't start in tinycore64 because of following dmesg:

"ioctl32(aterm:10310): Unknown cmd fd(5) cmd(00005302){t:'S';sz:0} arg(080606ae) on /dev/pts/0"

What means this ? It's to hard for me. Can anyone help ?

[mark]

Hallo Arslan S.,

I have to use puel lic. virtualbox (because USB/vRDP), so I successfully compiled the 64 bit virtualbox kernel module (from VirtualBox-3.2.6-Linux_amd64.run) and loaded (checked lsmod, and no errors in syslog), but the 64 bit virtualbox application itself cannot run, with errors: Invalid elf header.
Though I can compile and run the 32 bit virtualbox on the same tinycore (3.0/64bit).
I need a 64 version virtualbox, so how I can run the 64 bit apps vith tinycore?
(All of dependency remastered already into tinycore for this /toolchain64,gcc,compiletc,...etc./)
Please help! thx!

[Arslan S.]

all i know is only kernel related stuff is 64 bit inside microcore64 all others are the same as in microcore, that is 32 bit libraries, applications etc.

so there is no 64 bit extensions in repository except some kernel modules and toolchain64

and you should be able run 32 bit vbox with 64 bit vbox kernel modules because they are compiled exactly from the same source but with different compilers

for running 64 bit version of vbox you need to compile all its dependencies 64 bit i think (someone correct me if i am wrong please

[^thehatsrule^]

There's toolchain64-lib, but there may be some settings needed to be able to hook into it

[ricky]

After installing the new linux-headers-2.6.33.3-tinycore.tcz of ^thehatsrule^ in tinycore64-3.x, I was running VirtualBox-3.2.6-63112-Linux_amd64.run in tinycore64-3.x. It compiled (I think in 32-bit) and installed in /opt/VirtualBox very well, but without vbox kernel modules. After that I installed the already compiled vbox kernel modules (depmod -a, modprobe and so on...) and the messages were o.k. so far.
But when I did "sudo VirtualBox" in the Terminal (aterm), I received "/usr/bin/VirtualBox: exec: line 105: /opt/VirtualBox/VirtualBox: not found". As I looked in /opt/VirtualBox the file VirtualBox was present..

Why it can't find this file although is present ? Is that a mistake of the linux-headers or of busybox ?

[Arslan S.]

i dunno if it works but it is worth trying, i have seen some python scripts in vbox source, so:

Code: [Select]

tce-load -i python
sudo ln -sf /usr/local/bin/python /usr/bin/python

[ricky]

Hallo Arslan S.,
thank you for your advice. But python was already loaded, because it was necessary to compile VirtualBox. So I tried your second command . But after "sudo VirtualBox" i received the same message as before (see my last post yesterday).In tinycore3.0 (32-bit) no such problem.
So I am waiting for a new advice.

[ricky]

I think the problem is, that I need linux-headers-2.6.33.3-tinycore64.tcz too.
Is there a prospect to get that extension sooner or later ?

[mark]

Hallo Arslan S.,

I asked, the VirtualBox guys said 64 bit kernel modules+32 virtualBox apps combination not working unfortunately, so I think I can choose two different solution:
1. I switch back completly to 32 bit TC (this way I will lost the modern Core* CPUs 64 bit performance, but this way still I get very small host OS footprint & easy TC build/remaster)
2. I switch to completly to 64 bit TC (this way I have to build 64 bit libs+apps, this way I get not just very small footprint, but good performance also, though this will lot of not easy work)

So is there any plan to build a 64 bit TC completely?

If not, would be good some help how I can build it...
Maybe either way have to decide the future of TC:
1. support only older machine (but exist the 64 bit CPUs already several years)
2. support also a modern 64 bit CPU-s possibility (need more complicated repository & it's handling)

[dWLkR]

hi guys!

nice discussion that evolved around here in my thread!

thank you for your efforts - i think it would be great having a small-footprint-OS like TCL - so one is able to easily kick-start VMs without having a blown up host-OS...

i would love to see a stable release for the TCL-app-manager - please keep up the good work...

[Arslan S.]

Hallo Arslan S.,

I asked, the VirtualBox guys said 64 bit kernel modules+32 virtualBox apps combination not working unfortunately, so I think I can choose two different solution:
1. I switch back completly to 32 bit TC (this way I will lost the modern Core* CPUs 64 bit performance, but this way still I get very small host OS footprint & easy TC build/remaster)
2. I switch to completly to 64 bit TC (this way I have to build 64 bit libs+apps, this way I get not just very small footprint, but good performance also, though this will lot of not easy work)

So is there any plan to build a 64 bit TC completely?

If not, would be good some help how I can build it...
Maybe either way have to decide the future of TC:
1. support only older machine (but exist the 64 bit CPUs already several years)
2. support also a modern 64 bit CPU-s possibility (need more complicated repository & it's handling)

i am not the official here but i know that 64 bit apps are not accepted to the repository, for a complete 64 bit tc we need a completely different repository

also 32 bit vbox is the easiest way, i don't think the performance or other gains from 64 bit vbox will be worth all the efforts

if you really need vbox 64 bit i recommend arch linux
https://bbs.archlinux.org/viewtopic.php?pid=631681#p631681