Results 1 to 6 of 6

Thread: Not able to start VirtualBox kernel modules

  1. #1

    Exclamation Not able to start VirtualBox kernel modules

    Hallo,
    I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:

    /etc/init.d/vboxdrv setup

    I get this error:

    Stopping VirtualBox kernel modules done
    Uninstalling old VirtualBox DKMS kernel modules done
    Trying to register the VirtualBox kernel modules using DKMS done
    Starting VirtualBox kernel modules failed
    (modprobe vboxnetflt failed. Please use 'dmesg' to find out why)

    When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error:

    FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format

    I was stuck here, may I know what should I do in order to get my VB to be able to connect to the internet?

    THanks @!

  2. #2

    Default Re: Not able to start VirtualBox kernel modules

    Hi!

    That's strange for me that it installed using DKMS, it didn't for me on about 10 different installations since it was first implemented in VirtualBox.

    Try uninstalling all virtualbox related packages using yast (including kernel modules), then downloading and installing proper 4.0.4 package for 11.4 using rpm -Uhv. Worked for me every time.

  3. #3

    Default Re: Not able to start VirtualBox kernel modules

    I shouldn't imagine it's the ose version you want, it has some limitations that the standard version doesn't (or used to anyway)

    The rpm relevant to the version of suse you're using from Linux_Downloads - VirtualBox may work better for you, it's the page to get the version Aekold suggested

  4. #4

    Default Re: Not able to start VirtualBox kernel modules

    unless you use bridged networking (vboxnetflt.ko module) I'm not sure it matters, does VirtualBox start up?
    openSUSE Leap 42.1 x64, Plasma 5 & KDE 4.14.x, pretty current proprietary Nvidia drivers (self-compiled)

  5. #5

    Default Re: Not able to start VirtualBox kernel modules

    THank you so much for the reply.

    @Aekold and @Ecky
    Thanks for the suggestion, the version that I am using now, is the link that you suggest to me.

    @google01103
    At first my VB do not start, that is because I was using the YaST's version. After that I remove it and download the fresh one from the link suggested by Aekold. It is able to start now but the network is not working cos I am using the Bridge network. Some one from the VirtualBox.org forum suggest me to use NAT instead of Bridge. I did follow his suggestion and it is working fine now.

    Just curious to know why the Bridge network is not working?

    THanks @!

  6. #6

    Default Re: Not able to start VirtualBox kernel modules

    vboxnetflt is the module that provides bridge networking and since it can't be inserted it can't be access. In the VirtualBox forums there's a thread on this that suggests to install the dkms package from Packman PackMan :: Informationen zum Paket dkms but it made no difference to me - the vboxnetflt still did not insert (of course ymmv)
    openSUSE Leap 42.1 x64, Plasma 5 & KDE 4.14.x, pretty current proprietary Nvidia drivers (self-compiled)

Tags for this Thread

Posting Permissions

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