Error while setup Virtualbox on OpenSUSE 11

Hi folks!
Can you help me why I can’t run VirtualBox. I insert the content of “vbox-install.log” file below:


make KBUILD_VERBOSE=1 -C /lib/modules/2.6.25.5-1.1-default/build SUBDIRS=/tmp/vbox.9 SRCROOT=/tmp/vbox.9 modules
make[1]: Entering directory /usr/src/linux-2.6.25.5-1.1-obj/i386/default' make -C /usr/src/linux-2.6.25.5-1.1 O=/usr/src/linux-2.6.25.5-1.1-obj/i386/default/. modules make -C /usr/src/linux-2.6.25.5-1.1-obj/i386/default \ KBUILD_SRC=/usr/src/linux-2.6.25.5-1.1 \ KBUILD_EXTMOD="/tmp/vbox.9" -f /usr/src/linux-2.6.25.5-1.1/Makefile \ modules /usr/src/linux-2.6.25.5-1.1/scripts/gcc-version.sh: line 25: gcc: command not found /usr/src/linux-2.6.25.5-1.1/scripts/gcc-version.sh: line 26: gcc: command not found make[3]: gcc: Command not found test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \ echo; \ echo " ERROR: Kernel configuration is invalid."; \ echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \ echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo; \ /bin/false) mkdir -p /tmp/vbox.9/.tmp_versions ; rm -f /tmp/vbox.9/.tmp_versions/* make -f /usr/src/linux-2.6.25.5-1.1/scripts/Makefile.build obj=/tmp/vbox.9 gcc -Wp,-MD,/tmp/vbox.9/linux/.SUPDrv-linux.o.d -nostdinc -isystem -D__KERNEL__ -Iinclude -Iinclude2 -I/usr/src/linux-2.6.25.5-1.1/include -include include/linux/autoconf.h -I/tmp/vbox.9 -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Os -msoft-float -mregparm=3 -freg-struct-return -march=i586 -ffreestanding -pipe -Wno-sign-compare -I/usr/src/linux-2.6.25.5-1.1/include/asm-x86/mach-generic -Iinclude/asm-x86/mach-generic -I/usr/src/linux-2.6.25.5-1.1/include/asm-x86/mach-default -Iinclude/asm-x86/mach-default -fno-omit-frame-pointer -fno-optimize-sibling-calls -fasynchronous-unwind-tables -I/lib/modules/2.6.25.5-1.1-default/build/include -I/tmp/vbox.9/ -I/tmp/vbox.9/include -I/tmp/vbox.9/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_X86 -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.9/linux/.tmp_SUPDrv-linux.o /tmp/vbox.9/linux/SUPDrv-linux.c /bin/sh: gcc: command not found make[4]: *** [/tmp/vbox.9/linux/SUPDrv-linux.o] Error 127 make[3]: *** [_module_/tmp/vbox.9] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory /usr/src/linux-2.6.25.5-1.1-obj/i386/default’
make: *** [vboxdrv] Error 2

You don’t have gcc installed.

hi! i have the same problem. gcc, kernel-source, automake, make are allready installed. Don’t know what can it be. Think that my mistake was when i downgraded the kernel-source, but in the same time recompilation didn’t work even when my kernel-source was updated. Sorry for my english. If someone have any ideas will be very glad.

try this:
sudo /etc/init.d/vboxdrv setup
if it fails, you probably have a bad version of virtualbox
try to install defaul OSE version of VirtualBox from opensuse page/repository
(note that OSE version doesnt support USB)

Solved. It was my fault.
On my machine is installed Xen Hypervisor. I had to open an VHD image. of course xen don’t understand this type of images. The solution to run this image only to convert it in XVA format with v2xva software.
I didn’t try to solve the problem in this way and decide to install VirtualBox.
Everything was fine during downloading RPM package from sun.com. Thanks to guys that made it possible easy to install VirtualBox on different linux platforms.
At first run I got a message from virtualbox that i haven’t install kernel-source.
I rechecked 3 times gcc, automake, make, kernel-source, kernel-syms and 3 times update and downgrade the kernel-source.
Some minutes ago i restarted my machine not in xen mode, but in default.
Recompiled my kernel of vbox with known command /etc/init.d/vboxdrv setup and get all done.
The solution: if you really have all needed components installed and you are in xen mode, then you have to restart you computer in default mode and all will be fine.
Thanks for replies.
Suppose if someone will get in this trouble this is the solution.