Module build fails on 2.6.5 kernel (SuSE 9.1 Pro)

Ninho · Post by **Ninho** » 5. Jan 2009, 21:31

Hi! In trying to migrate from VMware to VBox, I experienced failed module compilation; I was referred to this forum as, I was told, the fine people from SUN/VB hang out here and shall be happy to oblige.

From a cursory glance at the (below appended listing), it would appear some IFDEF... statements based on kernel version are inaccurate in the header script called the-linux-kernel.h (leading to attempted redefinition of the msec-to-jiffies function and its converse)

Unfortunately the intricacies of the conditional defines plus my own limitations with C/C++ forbid me to diagnose precisely, even less repair the error(s) [like trains, errors can mask one another] ;=)

In advance, a full thank you ! Also in anticipation, I shall note that my kernel version is not very old and certainly one which VBox says is supported. Upgrading this system is unfortunately not an option ATM.

________________________________________________________
Installing VirtualBox to /opt/VirtualBox-2.1.0

Output from the module build process (the Linux kernel build system) follows:

make KBUILD_VERBOSE=1 -C /lib/modules/2.6.5-7.276-default/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
make -C ../../../linux-2.6.5-7.276 O=../linux-2.6.5-7.276-obj/i386/default modules
make -C /usr/src/linux-2.6.5-7.276-obj/i386/default                \
KBUILD_SRC=/usr/src/linux-2.6.5-7.276             KBUILD_VERBOSE=1        \
KBUILD_CHECK= KBUILD_EXTMOD="/tmp/vbox.0"        \
        -f /usr/src/linux-2.6.5-7.276/Makefile modules
mkdir -p /tmp/vbox.0/.tmp_versions
make -f /usr/src/linux-2.6.5-7.276/scripts/Makefile.build obj=/tmp/vbox.0
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -Iinclude2 -I/usr/src/linux-2.6.5-7.276/include  -I/tmp/vbox.0 -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -pipe -msoft-float -mpreferred-stack-boundary=2 -funit-at-a-time -funit-at-a-time -march=i586 -mregparm=3 -I/usr/src/linux-2.6.5-7.276/include/asm-i386/mach-default -Iinclude/asm-i386/mach-default -O2 -fomit-frame-pointer  -I/lib/modules/2.6.5-7.276-default/build/include  -I/tmp/vbox.0/  -I/tmp/vbox.0/include  -I/tmp/vbox.0/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 -DKBUILD_BASENAME=SUPDrv_linux -DKBUILD_MODNAME=vboxdrv -c -o /tmp/vbox.0/linux/.tmp_SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
In file included from /tmp/vbox.0/linux/SUPDrv-linux.c:38:
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:137: error: redefinition of `jiffies_to_msecs'
/usr/src/linux-2.6.5-7.276/include/linux/jiffies.h:74: error: `jiffies_to_msecs' previously defined here
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:148: error: redefinition of `msecs_to_jiffies'
/usr/src/linux-2.6.5-7.276/include/linux/jiffies.h:96: error: `msecs_to_jiffies' previously defined here
make[4]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Erreur 1
make[3]: *** [_module_/tmp/vbox.0] Erreur 2
make[2]: *** [modules] Erreur 2
make[1]: *** [modules] Erreur 2
make: *** [vboxdrv] Erreur 2

End of the output from the Linux kernel build system.
Installation successful
__________________________________________________________

http://www.virtualbox.de/wiki/User_FAQ · Post by **stefan.becker** » 5. Jan 2009, 21:35

I think its better to use a modern distribution like suse 11.x instead of dead horses.

Ninho · Post by **Ninho** » 6. Jan 2009, 12:46

Hi, Stefan.Becker ! I'm afraid, and sorry, I don't know the people here yet; are you expressing your own opinion or speaking on behalf of a responsible entity ? *** Please note I'm seeking effective help from the VB/Sun team, as my Linux distro and kernel are explicitly supported, according to the Fine Manual. this kernel furthermore is the latest official security update for SuSE 9.1***

My question still holds unchanged : can I receive practical instructions for modifying the source/headers as needed to compile the module ?

If however it were impossible, I would think the manuals and all the advertising relative to VBox support of Lçinux distros and kernels should be amended to reflect the truth rather than mirages. But at this point I'm still suspecting Stefan.Becker's views are those of an uninformed individual (of good will certainly) and do not reflect SUN and the VBox team's refusal to help repair a failing installation on a supported system.

--
Ninho

Ninho · Post by **Ninho** » 7. Jan 2009, 10:21

Now gents please, how can I circumvent this bug ?

Is there a more appropriate place than this forum for users to report bugs and get help from the people who put up the code or understand it ?

In the meanwhile : can someone tell me how to remove Birtualbox from this Linux box ? Starting the installation executable with some parameter, or what else ?

TIA !

--
Ninho

Post by **greenpossum** » 7. Jan 2009, 11:14

Ninho wrote:*** Please note I'm seeking effective help from the VB/Sun team, as my Linux distro and kernel are explicitly supported, according to the Fine Manual. this kernel furthermore is the latest official security update for SuSE 9.1***

Are you perhaps confusing SUSE Linux Enterprise 9 SP1 with SUSE 9.1? SUSE 9.1 is the community distro, which nowadays is called OpenSUSE and is at version 11.1. SUSE 9.1 has been long out of support. Which distro do you really have, the enterprise one from Novell or the community one?

Ninho · Post by **Ninho** » 7. Jan 2009, 11:24

greenpossum wrote: Which distro do you really have, the enterprise one from Novell or the community one?

I have SUSE (R) LINUX Professional 9.1, distributed by Novell Customer Communities, as part of their Linux Technical Resource Kit (summer 2004).

Thanks for caring !

--
Ninho

Post by **greenpossum** » 7. Jan 2009, 11:34

Ninho wrote:
greenpossum wrote: Which distro do you really have, the enterprise one from Novell or the community one?
I have SUSE (R) LINUX Professional 9.1, distributed by Novell Customer Communities, as part of their Linux Technical Resource Kit (summer 2004).

Despite the Professional in the name, this one is not the Enterprise version but is actually the consumer version. So it has been long out of support (2 years from date of release). Novell probably distributed it for free as trial software.

It should be added, even though SUSE Linux was not an Enterprise distro, it was one of the best constructed and loved distros and had a wide range of software included. Many people, including me, found it eminently suitable for server use. In those days SUSE Linux was not available over the Net, only on pressed CDs and DVDs. The community OpenSUSE distro was spun-off by Novell when they acquired SUSE.

As others have said, you really need a more up-to-date distro to have a more up-to-date kernel.

Ninho · Post by **Ninho** » 7. Jan 2009, 13:24

Yes, I know the "Professional" qualifier was dropped from subsequent iterations - but you asked what version I have actually, so I told you accurately I think. Also bundled was Entreprise Server 9 which I don't use.

greenpossum wrote: As others have said, you really need a more up-to-date distro to have a more up-to-date kernel.

Do I ? No I don't. I and my machine are fulfilled with this distro, we don't need or want to update.

VirtualBox explicitly says it supports SUSE 9.1 (among other Linux versions) and explicitly says it supports version 2.4 & 2.6 kernels. Therefore I think I can reasonably ask for help in making the necessary modules compile. ICBVW but it appears plausible that one or two cosmetic changes to the C header file could resolve the conflict seen in the log I posted.

Thank you very much for your input.

Post by **greenpossum** » 7. Jan 2009, 13:42

Ninho wrote:VirtualBox explicitly says it supports SUSE 9.1 (among other Linux versions) and explicitly says it supports version 2.4 & 2.6 kernels.

Where does it say that SUSE 9.1 is supported? On the list of downloads I can only see packages for recent OpenSUSE distros, and SLES10. But I suppose there is no incentive for Sun to provide packages for out-of-support distros.

As for building from source I don't know where it mentions the supported kernel versions, perhaps you can point out the web page?

Ninho · Post by **Ninho** » 7. Jan 2009, 14:04

greenpossum wrote:Where does it say that SUSE 9.1 is supported?
...
As for building from source I don't know where it mentions the supported kernel versions, perhaps you can point out the web page?

Both are stated very explicitly in the VBox manual (pdf), section 1.4.

Supported host operating systems
(...)
- SUSE Linux 9 and 10, ...
...

The same section says Linux kernel 2.6 is supported, however /starting with VirtualBox 2.1, kernel 2.4 is no more/. Point taken, and irrelevant since I have 2.6.5 - /and/ a supported distro.

Will you please help me escalate this problem in case this forum can be of no help ? Also, pray tell what the command is to cleanly remove the unusable Virtualbox installation, pending problem resolution - which I begin to think will take longer than was expected at first ;=(

Post by **greenpossum** » 7. Jan 2009, 14:20

Ninho wrote:Will you please help me escalate this problem in case this forum can be of no help ? Also, pray tell what the command is to cleanly remove the unusable Virtualbox installation, pending problem resolution - which I begin to think will take longer than was expected at first ;=(

I'm just an end-user like you, with no affiliation to Sun. You should file a bug report at the bugtracker site of Virtualbox if you believe that the documentation is misleading.

I suspect the documentation is somewhat out-of-date, or at least needs to be qualified with details. I suspect that nobody at Sun has tried building against the older 2.6 kernel in SUSE 9.1 simply because nobody has such a machine anymore. (But they could I suppose run 9.1 in a VM on a newer OpenSUSE for building purposes.

Anyway I can't help you with this any further, you would have to go to the bugtracker site.

Ninho · Post by **Ninho** » 7. Jan 2009, 14:28

greenpossum wrote: I'm just an end-user like you, with no affiliation to Sun. You should file a bug report at the bugtracker site of Virtualbox if you believe that the documentation is misleading.
.....
Anyway I can't help you with this any further, you would have to go to the bugtracker site.

Your contribution is welcome, Greenpossum. I'll do my best to find the bugtracker and bring this bug to the attention of SUN. Let's hope I do not have to meet again with the usual "you should upgrade your version" responses ...

Post by **sej7278** » 7. Jan 2009, 14:51

you are running suse pro 9.1 for some reason.

virtualbox supports suse linux enterprise server 9sp1 and newer.

these are entirely different entities, pro is about 5 years old for a start.

if you want support you can pay sun for a support contract, but nowhere do they state that they support suse PRO 9.1, so you can't really file a bug report either.

easier would be to update to something newer.

Ninho · Post by **Ninho** » 7. Jan 2009, 16:27

I do not think I should have to need repeat the same argument forever.
Who are you to make up such fantasies ? If you are not an authorised spokesperson for Sun/VBox, neither have any practical solution to help solving the question at hand, please spare us your ramblings; at least go read the reference I gave you above !

For the last time, the manual, version 2.1.0, says supported SUSE Linux 9 and 10, openSUSE 10.1, 10.2, 10.3 and 11. No mention of entreprise or otherwise. The manual also states the module should compile on all 2.6 kernels (earlier versions covered 2.4 and 2.6).

Contrary to your invaluable opinion, I believe there is an evident bug which has to be reported and acted upon - which I am going to port to Sun's bugtracker.

Regards

--
Ninho

Post by **sej7278** » 7. Jan 2009, 17:19

Ninho wrote:I do not think I should have to need repeat the same argument forever.
Who are you to make up such fantasies ? If you are not an authorised spokesperson for Sun/VBox, neither have any practical solution to help solving the question at hand, please spare us your ramblings; at least go read the reference I gave you above !

For the last time, the manual, version 2.1.0, says supported SUSE Linux 9 and 10, openSUSE 10.1, 10.2, 10.3 and 11. No mention of entreprise or otherwise. The manual also states the module should compile on all 2.6 kernels (earlier versions covered 2.4 and 2.6).

Contrary to your invaluable opinion, I believe there is an evident bug which has to be reported and acted upon - which I am going to port to Sun's bugtracker.

i'm going to have to restrain myself here for fear of being banned, but:

1. what is your obsession with talking to sun personnel only - if you want to do that then pay for a support contract, don't come to a COMMUNITY forum.

2. its kind of obvious that the manual refers to SLES enterprise 9 and 10 and not suse pro, as there was no suse pro 10! also by "2.6 kernel support", i don't think they mentionned all possible combinations of modules and config settings of any version of 2.6.x

3. maybe raise a bug report against the manual so it can be clarified, but its nothing to do with the software.

can a moderator please close this thread?