LinuxQuestions.org - VirtualBox vs Kernel 2.6.32 x86

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - VirtualBox vs Kernel 2.6.32 x86_64 (https://www.linuxquestions.org/questions/slackware-14/virtualbox-vs-kernel-2-6-32-x86_64-a-781188/)

VirtualBox vs Kernel 2.6.32 x86_64

If others are have the problem of VirtualBox failing to build the kernel modules with kernel 2.6.32 try this :-

1. Install VirtualBox and watch as the kernel modules fail to compile.

2. Change the line

Code:

KFLAGS += -DRT_ARCH_AMD64

Code:

KFLAGS += -DRT_ARCH_X86_64

In the following files :-

Code:

Line 231 /opt/VirtualBox/src/vboxdrv/Makefile

Line 170 /opt/VirtualBox/src/vboxnetadp/Makefile

Line 174 /opt/VirtualBox/src/vboxnetflt/Makefile

3. Run /etc/rc.d/rc.vboxdrv setup

You will now have a working VirtualBox setup

NB This is written purely from the standpoint of using the Closed source version of VB not the OSE version.

I have VirtualBox 3.1.2 PUEL edition installed on top of a Slackware64-13.0 with 2.6.32.2 and encountered no compilation problem :scratch:

I have at last been able to isolate the trigger, if like me you use SlackBuilds a lot you probably have ARCH set to avoid changing each script.

If ARCH=x86_64 is set VirtualBox will attempt for some reason to pass amd64 to the kernel build this is invalid in the kernel as amd64 is not used as a architecture name instead x86_64 is used.

PS Pat just released .3 in -current