Results 1 to 6 of 6

Thread: virtualbox broken by kernel upgrade

  1. #1
    Join Date
    Aug 2008
    Location
    England
    Posts
    63

    Default virtualbox broken by kernel upgrade

    I have just installed the kernel through the update manager. The kernel-default package is now 4.1.15-8.1 as are the associated devel packages.
    Virtualbox now does not run a virtual machine with details:
    Code:
    The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1).
      
    
    Result Code: NS_ERROR_FAILURE (0x80004005)
    Component: MachineWrap
    Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
    It also provides a window called "VirtualBox - Error In suplibOsInit" with content:

    Code:
    Kernel driver not installed (rc=-1908)
    
    The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
    
    '/sbin/vboxconfig'
    
    as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
    
    where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

    There is no file '/sbin/vboxconfig'

    I have run:

    Code:
    sudo /usr/sbin/rcvboxdrv setup
    but this does not solve the problem returning:

    Code:
    Recompiling VirtualBox kernel module, NOT. It has been packaged.                          done
    I have tried upgrading the VirtualBox packages using Yast but that did not help.

    Any ideas anyone?

  2. #2
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    16,745

    Default Re: virtualbox broken by kernel upgrade

    You probably just need to reload the module. I've run into that myself.

    Something else that I noticed with the most recent VirtualBox update was
    that one of my VMs said it needed a new extensions package. For some
    reason, other VMs didn't have that problem.

    You also want to shut down any running VMs before running either a kernel
    update or a VirtualBox update - otherwise, you end up not being able to
    manage them.

    For your issue, try:

    sudo modprobe vboxdrv

    That should take care of it.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  3. #3
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    16,745

    Default Re: virtualbox broken by kernel upgrade

    You probably just need to reload the module. I've run into that myself.

    Something else that I noticed with the most recent VirtualBox update was
    that one of my VMs said it needed a new extensions package. For some
    reason, other VMs didn't have that problem.

    You also want to shut down any running VMs before running either a kernel
    update or a VirtualBox update - otherwise, you end up not being able to
    manage them.

    For your issue, try:

    sudo modprobe vboxdrv

    That should take care of it.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  4. #4
    Join Date
    Aug 2008
    Location
    England
    Posts
    63

    Default Re: virtualbox broken by kernel upgrade

    Thanks Jim, that modprobe works for me.

  5. #5

    Default Re: virtualbox broken by kernel upgrade

    Quote Originally Posted by pblewis View Post
    Thanks Jim, that modprobe works for me.
    I had the same issue. I have left no stone unturned to apply all the combinations mentioned in this post. Alternatively, I gave it a try to have the virtualbox installed from their website instead of the Opensuse-provided one. It has luckily worked out of the box, and without any kernel rebuilding.

  6. #6

    Default Re: virtualbox broken by kernel upgrade

    Quote Originally Posted by hendersj View Post
    You probably just need to reload the module. I've run into that myself.

    Something else that I noticed with the most recent VirtualBox update was
    that one of my VMs said it needed a new extensions package. For some
    reason, other VMs didn't have that problem.

    You also want to shut down any running VMs before running either a kernel
    update or a VirtualBox update - otherwise, you end up not being able to
    manage them.

    For your issue, try:

    sudo modprobe vboxdrv

    That should take care of it.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

    Thanks for the tip - this worked Tumbleweed as well

Posting Permissions

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