Home IT Linux Windows Database Network Programming Server Mobile  
  Home \ Linux \ VirtualBox virtual machine can not start to solve under Ubuntu     - MySQL database to open a remote connection method (Database)

- How to create a someone project on github (Linux)

- ORA-00600 error solve one case (Database)

- Hazelcast integration with MongoDB (Database)

- Introduction to Linux system process monitoring tools (Linux)

- Getting Started with Linux system to learn: how to use tcpdump to capture TCP SYN, ACK and FIN packets (Linux)

- CentOS installation Docker series (Linux)

- CentOS6 5 Configure SSH password Free (Linux)

- How linux network security configuration (Linux)

- Btrfs file system creation and their characteristics in Linux (Linux)

- Linux environment to configure Apache + Django + wsgi (Server)

- Ceph single / multi-node installation summary Powered by CentOS 6.x (Server)

- VMware installed Linux system and JDK deployment (Linux)

- Django1.5 Custom User Model (Programming)

- Necessity in Java packages (Programming)

- Linux program analysis tool: ldd and nm (Linux)

- Use netcat [nc] command on Linux and Unix port scan (Server)

- Compare Dalvik virtual machine and the JVM (Linux)

- Linux account management add relevant directives (Linux)

- Ubuntu 14.04 build Gitlab (Linux)

  VirtualBox virtual machine can not start to solve under Ubuntu
  Add Date : 2018-11-21      
  Recently in a number of virtual machines for Hadoop debugging, so in the installation of VirtualBox virtual machine on Ubuntu, but encountered a virtual machine can not start the problem:

Interface will pop up an error dialog box, the error message is as follows:

Kernel driver not installed (rc = -1908)

The VirtualBox Linux kernel driver (vboxdrv) is neither loaded or there is a permission problem with / dev / vboxdrv. Re-setup the kernel module by executing

'/etc/init.d/vboxdrv setup'

As root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

First summarize the system environment: ubuntu desktop 13.10, virtualbox-4.3, kernel: 3.11.0-17

1. In accordance with this error instructions, I switched to the command line,

Sudo /etc/init.d/vboxdrv setup

 Get the following error message:

Suggesting still unable to load dkms normal, and it seems the need to compile the current source code of the kernel, at the same time, suggested that /var/log/vbox-inuntustall.log suggested that the log.

2. Then, cat / var / log / vbox-install logs

 Uninstalling modules from DKMS
  Remove old DKMS module vboxhost version 4.3.8

Deleting module version: 4.3.8
Completely from the DKMS tree.
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxhost/4.3.8/source ->

DKMS: add completed.
Failed to install using DKMS, attempting to install without
Makefile: 183: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR = < directory> and run Make again. Stop.

These little do not know what went wrong, where a problem?

 3. Check dkms, normal installation; repeated installation virtualbox, to ensure that the installation is not caused by incomplete problems.

Sudo apt-get install dkms

Hint has been installed to the latest version, the problem should not dkms.

4. View the kernel version uname-r, get the current kernel version: 3.11.0-17-generic.

5. Search for a bit of the network, it was suggested that may need to re-install the kernel.

Sudo apt-get install linux-headers - $ (uname -r)

Note: $ {uname-r} used to represent the current version of the kernel can not be used directly in the command, where my version is step 4 in the output.

6. Follow the previous prompts to re-run sudo /etc/init.d/vboxdrv setup

Www.linuxidc.com @linuxidc: ~ $ sudo /etc/init.d/vboxdrv setup
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 ... done.

Tip: VirtualBox module has been registered to the normal kernel

7. Then you can click the virtualbox start button, virtualbox virtual machine to start the normal.

8. Reason analysis:

Finally, I try to analyze a moment, the reason for this error: before the virtualbox is working properly, and later upgraded ubuntu and kernel version, the estimated virtualbox and kernel before breaking the registration system is the original registered in the new kernel In the failure of the same time, the kernel may be in the upgrade process, there are a number of instability. Therefore, the need to re-cover the installation of the kernel, and then once again virtualbox kernel registered to the current Linux kernel, the above is only speculation, welcome to put forward new ideas and speculation.
- Java abstract class instantiation (Programming)
- JBPM6 Installation and Configuration Tutorial (Linux)
- CentOS7 installation configuration Redis-3.0.0 (Database)
- Linux system - The understanding cpu load (Linux)
- To add the Oracle JDBC driver in Maven repository (Linux)
- Linux how to view your JDK installation (Linux)
- Generic mechanism C11 standard (Programming)
- Docker build their own private warehouses (Linux)
- Setting grep Highlight Matches (Linux)
- shell script: MySQL monitoring service is normal (Database)
- Ubuntu install Vendetta Online 14.04 (Linux)
- Linux into single user mode to modify the administrator password (Linux)
- Linux Firewall Basics (Linux)
- How to manage and use Logical Volume Management LVM in Ubuntu (Linux)
- Lua and C ++ (Programming)
- Linux Mint brightness adjustment --xrandr command learning (Linux)
- Linux system firewall defense network attacks (Linux)
- C # socket udp broadcast (Programming)
- OpenVPN offsite interconnecting room availability and load balancing solution (Server)
- Linux crontab command format example (Linux)
  CopyRight 2002-2016 newfreesoft.com, All Rights Reserved.