Trouble installing Virtualbox

I tried installing VirtualBox-4.2-4.2.6_82870_openSUSE114-1.i586 on openSUSE 11.4. But I am not able to do it.
I used the following commands


zypper install VirtualBox-4.2-4.2.6_82870_openSUSE114-1.i586.rpm 
Loading repository data...
Warning: Repository 'Updates for openSUSE 11.4 11.4-0' appears to outdated. Consider using a different mirror or server.
Reading installed packages...
Resolving package dependencies...

The following NEW packages are going to be installed:
  libpng12-0 VirtualBox-4.2 

2 new packages to install.
Overall download size: 61.4 MiB. After the operation, additional 136.6 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package libpng12-0-1.2.49-16.1.i586 (1/2), 72.0 KiB (166.0 KiB unpacked)
Retrieving: libpng12-0-1.2.49-16.1.i586.rpm [done (38.5 KiB/s)]
Retrieving package VirtualBox-4.2-4.2.6_82870_openSUSE114-1.i586 (2/2), 61.4 MiB (136.5 MiB unpacked)
Installing: libpng12-0-1.2.49-16.1 [done]
Retrieving package VirtualBox-4.2-4.2.6_82870_openSUSE114-1.i586 (1/2), 61.4 MiB (136.5 MiB unpacked)
Installing: VirtualBox-4.2-4.2.6_82870_openSUSE114-1 [done]
Additional rpm output:
warning: /var/cache/zypp/packages/_tmpRPMcache_/VirtualBox-4.2-4.2.6_82870_openSUSE114-1.i586.rpm: Header V4 DSA/SHA1 Signature, key ID 98ab5139: NOKEY

Creating group 'vboxusers'. VM users must be member of that group!

No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Stopping VirtualBox kernel modules..done
Recompiling VirtualBox kernel modules..failed
  (Look at /var/log/vbox-install.log to find out what went wrong)


and this the log file.

Makefile:184: Warning: using /usr/src/linux as the source directory of your Linux kernel. If this is not correct, specify KERN_DIR=<directory> and run Make again.
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /usr/src/linux modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (        \
echo;                                \
echo "  ERROR: Kernel configuration is invalid.";        \
echo "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo "         Run 'make oldconfig && make prepare' on kernel src to fix it.";    \
echo;                                \
/bin/false)

  ERROR: Kernel configuration is invalid.
         include/generated/autoconf.h or include/config/auto.conf are missing.
         Run 'make oldconfig && make prepare' on kernel src to fix it.

mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*

  WARNING: Symbol version dump /usr/src/linux-2.6.37.6-24/Module.symvers
           is missing; modules will have no dependencies and modversions.

make -f scripts/Makefile.build obj=/tmp/vbox.0
/tmp/vbox.0/Makefile:184: Warning: using /usr/src/linux as the source directory of your Linux kernel. If this is not correct, specify KERN_DIR=<directory> and run Make again.
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d  -nostdinc -isystem /usr/lib/gcc/i586-suse-linux/4.5/include -I/usr/src/linux-2.6.37.6-24/arch/x86/include -Iinclude  -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fomit-frame-pointer -DCC_HAVE_ASM_GOTO -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -I/usr/src/linux/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxdrv/ -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/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 -DVBOX_WITH_64_BITS_GUESTS  -DMODULE  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)"  -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.0/linux/SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
/tmp/vbox.0/linux/SUPDrv-linux.c:1:0: error: code model ‘kernel’ not supported in the 32 bit mode
/tmp/vbox.0/linux/SUPDrv-linux.c:1:0: sorry, unimplemented: 64-bit mode not compiled in
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2


I am very new to linux and I don`t understand the log file.
Please help me fix this. Thanks in advance.

You are more likely to get good answers if you had posted the query here https://forums.opensuse.org/english/get-technical-help-here/virtualization/ (Questions about virtual machines as hosts and clients and in all operating systems)

On 2013-01-13 07:36, Ashiq is a Geek wrote:
>
> I tried installing VirtualBox-4.2-4.2.6_82870_openSUSE114-1.i586 on
> openSUSE 11.4. But I am not able to do it.

Virtual box questions must be asked in the virtualization subforum.
Please ask a moderator to move your post.

As you are new to Linux, I must warn you that 11.4 is old and with no
maintenance, except by the Evergreen project which I don’t think you are
using.

You should install 12.1 or 12.2.


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

CLOSED. Will be moved.

[QUAshiq_is_a_GeekOTE=hcvv;2517879]CLOSED. Will be moved.[/QUOTE]
OPEN again,

@Ashiq_is_a_Geek,
As the “official” 11.4 repos are no longer available, you probably use 11.4 repos from elsewhere. Which in itself in not a problem, except that when something is wrong there, nobody will repair that anymore. Also almost nobody here will use 11.4 anymore and thus recreating your problem will nor readily be possible.

Like Carlos, I advise you to upgrade to openSUSE 12.2.

Thanks for the support all of you… I shall move to 12.2 as early as possible…

On 2013-01-13 12:56, hcvv wrote:

> As the “official” 11.4 repos are no longer available, you probably use
> 11.4 repos from elsewhere.

No, the 11.4 repos are in place, because they are used as historical
data by the evergreen project.


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

Nevertheless I guess that their status is the same as those of older versions found at e.g. GWDG. Available and complete and usable, but with less and less conract with the rest of a moving environment.

On 2013-01-13 13:46, hcvv wrote:

> Nevertheless I guess that their status is the same as those of older
> versions found at e.g. GWDG. Available and complete and usable, but with
> less and less conract with the rest of a moving environment.

Of course, evergreen is an LTS, so that is precissely as intented. New
things, when available, are in the repos named “evergreen”, as the
evergreen update repository.

Thus the 11.4 update repo warns that it is old, but there is a new
update repo which is not. It is a different team who does the updates,
so they use different repos. The old update repo has to be kept there
because if you reinstall or install a package, you need to apply all the
updates that were created during the life of 11.4, and then the new
updates if they exist.


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

My guess is you may have the same problem with the latest openSUSE version if you adopt the same systemic approach. When installing a kernel-devel version in addition to a kernel, insure they are the same version. Unless one is experienced, I do not recommend installing multople different versions of boot kernels.