3.0.0_beta2 on kernel 2.6.27 [SLES11] not installable

[klaus_ph]

hi,
I'm so sorrry, to tell this. everybody who wants to follow, read please:

http://allegronet.de/vbox-install.log

VirtualBox-3.0.0_BETA1_48728_sles10.1-1.x86_64.rpm is not installable on my SLES11 (kernel linux-2.6.27.23-0.1)
today I will try to compile sources_package by myself.
Yours Klaus


NB1: forgotten to say. virtualbox = great work = very honorable! [Thank You]
NB2: there's is an old wxp_machine waiting, to get integrated in my sles_11_bomb. I want (and must) reduce electrific_costs . it's my internet_proxy and crashes sometimes (1x per week) down, lost internet for customers. an more than 10 years old IBM-netfinity with two hearts a 550MHZ netfinity reaches the end. [like "The Doors: this is the end"]

[frank]

Please use the universal Linux .run package to install VirtualBox on SLES11.

[klaus_ph]

Please use the universal Linux .run package to install VirtualBox on SLES11.

thanks a lot.
stupid boy [=mine!!!][=me] forgot the run_package.


installing with run_package works: (no error)
========================
xseries346:~ # ./vb_3002beta.run (=my filename)
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation........
VirtualBox Version 3.0.0_BETA2 r49051 (2009-06-24T14:56:23Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel module
Building the VirtualBox netflt kernel module
Building the VirtualBox netadp kernel module
VirtualBox has been installed successfully.
...
Press any key to continue...


next step:
=======
/etc/init.d/vboxdrv setup

but:
===
xseries346:/etc/init.d # ./vboxdrv setup
Stopping VirtualBox kernel module done
Removing old VirtualBox netadp kernel module done
Removing old VirtualBox netflt kernel module done
Removing old VirtualBox kernel module done
Recompiling VirtualBox kernel module done
Starting VirtualBox kernel module failed
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Press any key to continue...

who wants, read this please vbox-install.log on
http://allegronet.de/vbox-install.log
hope, it helps.

yours
klaus

NB: I have no problem to test this regularly for all (my basics: SLES11 2hearted XEON). It's in my personal interessest
If Frank Mehnert lives in Dresden, he could jump to Radeberg (beer-town), only 10km to north-east. Frank, it's an invitation!

MODEDIT: Removed your E-mail address as I assume that you don't want to be added to a SPAM list

[frank]

And yes, I really live in Dresden. But I thought that the Radeberger brewery is near to the Semperoper?

[frank]

Apart from this, please could you attach the output of dmesg after you executed /etc/init.d/vboxdrv setup?

[klaus_ph]

Apart from this, please could you attach the output of dmesg after you executed /etc/init.d/vboxdrv setup?

no, sir, impossible
dmesg is full with firewall_blockings.
there are definitely NO infos about our program. sorry for this.

other hint?

something like this:
1. /etc/init.d/vboxdrv setup >>vbockssätupp
=no useable result...

2. /etc/init.d/vboxdrv setup 2>vbockssättupp
= result
.7.[?25l
.[110C.[10D.[1;31mfailed.[m..8.[?25h
(no idea, what this could be...)

any hints? to follow, what happens
my hint: a buildin debug_modus in vboxdrv (=shell_skript) ???

NB: my email_adress in forum NO problem. I love viagra. must fetch alldays cheapest offers

[frank]

Please do

Code: Select all   Expand viewCollapse view

modprobe vboxdrv

. If the module load fails, have a look at the last few lines of dmesg. There must be some information why the kernel refuses to load the module.

[klaus_ph]

Please do

Code: Select all   Expand viewCollapse view

modprobe vboxdrv

. If the module load fails, have a look at the last few lines of dmesg. There must be some information why the kernel refuses to load the module.

xseries346:~ # modprobe vboxdrv

FATAL: module '/lib/modules/2.6.27.23-0.1-pae/misc/vboxdrv.ko' is unsupported

Use --allow-unsupported or set allow_unsupported_modules to 1 in
/etc/modprobe.d/unsupported-modules

ok. above is set to 1. it works. yeah.

dmesg:

vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 4 processor cores.
vboxdrv: fAsync=0 offMin=0x68a offMax=0x5271
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 3.0.0_BETA2 (interface 0x000e0000).
xseries346:/etc/modprobe.d #

great. does this help? I hope.....

ok. If I understand this very well right, than I will give another try to the vbox_package to run.
maybe it depends from "0" in unsopperted modules...

ok2:
xseries346:/etc/init.d # ./vboxdrv
Usage: ./vboxdrv {start|stop|stop_vms|restart|force-reload|status|setup}
xseries346:/etc/init.d # ./vboxdrv setup
Stopping VirtualBox kernel module done
Removing old VirtualBox netadp kernel module done
Removing old VirtualBox netflt kernel module done
Removing old VirtualBox kernel module done
Recompiling VirtualBox kernel module done
Starting VirtualBox kernel module done
xseries346:/etc/init.d #

dmesg:

vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 4 processor cores.
vboxdrv: fAsync=0 offMin=0x68a offMax=0x5271
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 3.0.0_BETA2 (interface 0x000e0000).
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 4 processor cores.
vboxdrv: fAsync=0 offMin=0x6f0 offMax=0x5cf0
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 3.0.0_BETA2 (interface 0x000e0000).

some hours later. being back in evening.
yours klaus


Nb: have something again learned...."allow_unsupported_modules", oh yeah man!

[klaus_ph]

ok, boys

it seems, vbox3.0.0beta2 will just now run on SLES11
there was some irratationes.

a small guideline
============
1. use VirtualBox-3.0.0_BETA2-49051-Linux_x86.run (for 86'er): certain is *.run (!)
2. enable unsupported modules in:
Use --allow-unsupported or set allow_unsupported_modules to 1 in
/etc/modprobe.d/unsupported-modules
[think about security!!!!! what does THIS means....I must also think about it...]
controll it with dmesg (thanks frank....)
3. install it with: /etc/init.d/vboxdrv setup
4. let him go with /etc/init.d/vboxdrv start
5. on graphical desktop, there is: /opt/VirtualBox/VirtualBox
5a. register yourself on SUN

I hope, not forget something. If yes, read THIS thread. the solution is IN it

bytheway: I You will get an update for Your existing kernel (vbox isn't integrated IN sles11), You must reinstall(?) or recompile(?) it. I have done this several times with SLES 10

NB: better for all would be: we get an rpm_package especially for SLES 11. (for SLES10 it exists)

[frank]

Actually Novell should start supporting the DKMS package as other distributions (Ubuntu, Fedora, Mandriva, ...) do. Installing DKMS and no further problems with kernel upgrades.

I have no idea what this allow_unsupported_modules means, sounds like something distribution-specific thing.