Results 1 to 10 of 10

Thread: VirtualBox kernel not match

  1. #1
    mfecit NNTP User

    Default VirtualBox kernel not match

    rpm-ivh VirtualBox2.0.0_36011_openSUSE11-1.i586.rpm
    (Linux_Downloads - VirtualBox)

    after that,I type
    /etc/init.d/vboxdrv setup

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


    vi /var/log/vbox-install.log
    Makefile:166: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop.


    notes:

    uname -r
    2.6.25.16-0.1-default

    ls /lib/modules/
    2.6.25.11-0.1-default
    2.6.25.11-0.1-pae
    2.6.25.16-0.1-default
    2.6.25.16-0.1-pae
    2.6.25.5-1.1-debug
    2.6.25.5-1.1-default
    2.6.25.5-1.1-pae

  2. #2
    Join Date
    Jun 2008
    Location
    UTC+10
    Posts
    9,686
    Blog Entries
    4

    Default Re: VirtualBox kernel not match

    You need the kernel-source (that matches the running kernel), kernel-headers, gcc, and make packages to be able to build the vboxdrv module.

  3. #3
    mfecit NNTP User

    Default Re: VirtualBox kernel not match

    I still got confused,especially for a newbie

    yum install kernel-source linux-kernel-headers gcc make

    rpm -q kernel-source linux-kernel-headers gcc make

    kernel-source-2.6.27-rc5.git9.6
    linux-kernel-headers-2.6.27-6
    gcc-4.3-55
    make-3.81-125


    uname -r
    2.6.25.16-0.1-default

  4. #4
    mfecit NNTP User

    Default Re: VirtualBox kernel not match

    Finally I uninstall VirtualBox2.0
    and yum install virtualbox
    (VirtualBox OSE 1.6.2)

    ****it,still kernel problem

    linux-vkg1:~/Desktop # /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel module done
    Recompiling VirtualBox kernel module, NOT. It has been packaged. done
    Starting VirtualBox kernel module failed
    (No suitable module for running kernel found)

  5. #5

    Default Re: VirtualBox kernel not match

    I ran into this issue as well yesterday after the kernel upgrade.

    If you don't already have the repo for VirtualBox, add it in and update OSE to 1.6.4. It worked fine after that.

    Index of /repositories/Virtualization:/VirtualBox/openSUSE_11.0

    Looks like they released v2.0.2 today as well.

    From the change log:
    Linux hosts: compile fixes for kernel module on Linux 2.6.27

    C.Durbin

  6. #6
    Join Date
    Jun 2008
    Location
    UTC+10
    Posts
    9,686
    Blog Entries
    4

    Default Re: VirtualBox kernel not match

    Quote Originally Posted by mfecit View Post
    I still got confused,especially for a newbie

    yum install kernel-source linux-kernel-headers gcc make

    rpm -q kernel-source linux-kernel-headers gcc make

    kernel-source-2.6.27-rc5.git9.6
    linux-kernel-headers-2.6.27-6
    gcc-4.3-55
    make-3.81-125


    uname -r
    2.6.25.16-0.1-default
    yum? zypper is the native tool of choice.

    It looks like you are getting bleeding edge kernels from some repo, and it doesn't match the running kernel. Here are the current versions after the recent kernel update:

    linux-kernel-headers-2.6.25-8.1
    kernel-source-2.6.25.16-0.1
    kernel-default-2.6.25.16-0.1

    The headers doesn't have to match in the RPM release version as the kernel's external API hasn't changed.

  7. #7

    Default Re: VirtualBox kernel not match

    Interesting...I am running:

    Kernel 2.6.25.16-0.1-pae

    With the correct source/header files and still couldn't get 2.0.0 to recompile/install properly. I just downloaded and installed 2.0.2 and it runs fine. They don't mention any problems with 2.6.25 in the changelog though.

    C.Durbin

  8. #8
    mfecit NNTP User

    Default Re: VirtualBox kernel not match

    Could someone just tell me the steps
    I just can't fix this

  9. #9

    Thumbs down Re: VirtualBox kernel not match

    I'm facing the same errors. I've just checked my kernel using

    uname -a

    Linux linux-1vmb 2.6.25.16-0.1-default #1 SMP 2008-08-21 00:34:25 +0200 x86_64 x86_64 x86_64 GNU/Linux

    I've just upgraded to virtualbox-ose-2.0.0-2.1.x86_64.rpm and all its cousins. The 1.6.4 edition and its cousins worked like a charm and now I get this blackheart:

    tom@linux-1vmb:~> sudo /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel module done
    Recompiling VirtualBox kernel module, NOT. It has been packaged. done
    Starting VirtualBox kernel module failed
    (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
    This is worth a

    Using dmesg provided me with:

    vboxadd: VirtualBox PCI device not found.
    vboxdrv: Unknown symbol RTHeapSimpleAlloc
    vboxdrv: Unknown symbol RTHeapSimpleFree
    vboxdrv: Unknown symbol RTHeapSimpleInit
    vboxadd: VirtualBox PCI device not found.
    vboxdrv: Unknown symbol RTHeapSimpleAlloc
    vboxdrv: Unknown symbol RTHeapSimpleFree
    vboxdrv: Unknown symbol RTHeapSimpleInit

    It looks like the product is not fully tested...

  10. #10

    Cool Re: VirtualBox kernel not match

    I've downloaded the binary (Yep, USB!!!) version of VBOX 2.02 for OpenSuSE 11 x64 edition. Before I've installed this beast I've uninstalled the VBOX 2.00 version from the OpenSuSE repositories and I've also fired the OpenSuse repository, since 2.00 made all my images inaccessible due to a 'dll-hell'.

    I'll stick with sun and I'll wait to upgrade before the show-stoppers are ironed out.

    Now I'm happy again. -

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •