Results 1 to 5 of 5

Thread: Upgrade from VirtualBox 2.1.0 to 2.1.2 vboxdrv issue

  1. #1

    Default Upgrade from VirtualBox 2.1.0 to 2.1.2 vboxdrv issue

    Hey everybody, I've already posted on the Vbox forums, but I want to post here to diversify. Here's the situation:

    OpenSuse 11.1 host. Vbox 2.1.0 was installed from binary. Upgraded to 2.1.2 earlier today (tried several times using rpm command-line and Yast). Yast doesn't report errors, but rpm on cli does. Error on install is "Stopping VirtualBox kernel module failed (Cannot unload module vboxdrv)."

    Dmesg reveals:
    vboxnetflt: no symbol version for SUPDrvLinuxIDC
    vboxnetflt: Unknown symbol SUPDrvLinuxIDC

    VirtualBox boots, but if I attempt to start a VM I get the following message:

    The VirtualBox support driver which is running is from a different version of VirtualBox. You can correct this by stopping all running instances of VirtualBox and reinstalling the software. (VERR_VM_DRIVER_VERSION_MISMATCH).

    Result Code:
    NS_ERROR_FAILURE (0x80004005)
    Component:
    Console
    Interface:
    IConsole {e3c6d4a1-a935-47ca-b16d-f9e9c496e53e}

    I have a feeling it's something fairly simple (deleting links or something) and re-running /etc/init.d/vboxdrv setup, but I'm new to OpenSuse and its software managers. Any help would be greatly appreciated.

  2. #2

    Default Re: Upgrade from VirtualBox 2.1.0 to 2.1.2 vboxdrv issue

    Figured it out. Looks like a couple of others were running into this issue so upgraders beware.

    I uninstalled everything to be safe. Rebuilt it from the rpm via command line. Restarted. Rebuilt the vboxdrv via "/etc/init.d/vboxdrv setup" (this time it works). Started the service with "/etc/init.d/vboxdrv start". Then made it permanent on reboot with "insserv vboxdrv"

    What ever happened to the days of not having to reboot Linux?

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

    Default Re: Upgrade from VirtualBox 2.1.0 to 2.1.2 vboxdrv issue

    You didn't really need to reboot, you only had to follow what was suggested, viz unloading the old vboxdrv module and rerunning setup.

    modprobe -r vboxdrv
    /etc/init.d/vboxdrv setup

    inserv wasn't needed either, it would have already been activated for boot.

  4. #4

    Default Re: Upgrade from VirtualBox 2.1.0 to 2.1.2 vboxdrv issue

    Problem was I couldn't modprobe -r vboxdrv. It would fail out on everything. Modprobes, /etc/init.d/vboxdrv start, stop, etc. It was attempting to unload something that wasn't loaded.

  5. #5
    Tilman Schmidt NNTP User

    Default Re: Upgrade from VirtualBox 2.1.0 to 2.1.2 vboxdrv issue

    chazsheen schrieb:
    > Problem was I couldn't modprobe -r vboxdrv. It would fail out on
    > everything. Modprobes, /etc/init.d/vboxdrv start, stop, etc. It was
    > attempting to unload something that wasn't loaded.


    That's normally not a problem. If the modules which the script
    wants to unload aren't loaded, the script proceeds normally.
    Happens all the time to me after compiling and booting a new
    kernel for which the vboxdrv module hasn't been recompiled yet.

    So there must have been some other problem.

    --
    Tilman Schmidt
    Phoenix Software GmbH
    Bonn, Germany

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
  •