Ubuntu-server 17.04 x64, Cinammon 3.2.7, Kernel 4.13.3 generic.  Attempting to set up VirtualBox, though so far I have been unable to start any virtual machine. Upon installation (apt install virtualbox), I get the following lines near the end of the installation process:  ● virtualbox.service - LSB: VirtualBox Linux kernel module Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-09-21 19:57:07 +04; 18ms ago Docs: man:systemd-sysv-generator(8) Process: 463 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE) CPU: 28ms  Sep 21 19:57:06 Hiigaran systemd[1]: Starting LSB: VirtualBox Linux kernel module... Sep 21 19:57:06 Hiigaran virtualbox[463]:  * Loading VirtualBox kernel modules... Sep 21 19:57:07 Hiigaran virtualbox[463]:  * No suitable module for running kernel found Sep 21 19:57:07 Hiigaran virtualbox[463]:    ...fail! Sep 21 19:57:07 Hiigaran systemd[1]: virtualbox.service: Control process exited, code=exited status=1 Sep 21 19:57:07 Hiigaran systemd[1]: Failed to start LSB: VirtualBox Linux kernel module. Sep 21 19:57:07 Hiigaran systemd[1]: virtualbox.service: Unit entered failed state. Sep 21 19:57:07 Hiigaran systemd[1]: virtualbox.service: Failed with result 'exit-code'.   Tried following the top answer in  question, by removing virtualbox-dkms and installing it again. This resulted in the same lines as above.  Attempting to start a virtual macine, I get an error giving the following details:  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 virtualbox-dkms package and load the kernel module by executing  'modprobe vboxdrv'  as root.  where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.    The modprobe command results in:  modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.13.3-041303-generic
9280
I tried to use my Virtual Box and this is the error I received - (I just updated to the new Ubuntu also) and I am VERY new at this Linux OS.     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      '/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.
80425
I have recently fallen in love with Linux. I first decided to try out Ubuntu 13.10 a few weeks ago, but I bricked it by incorrectly installing an AMD FGLRX driver. Then I reformatted and wiped that partition to try out Linux Mint 16. I did the same thing with Mint, as well as with Fedora 20, 19, and 18 (in that order). Now I am on a stable Ubuntu 12.04 because I know how to use it vastly more than the other distros I've tried and because it seems like it has the biggest online support group.  Because I am now tired of reformatting and reinstalling broken distros, I thought it would be a good idea to get at least one distro stable (Precise) and to test the driver installations and other risky modifications for that distro and others with them running in Oracle Virtual Box since I don't trust my Linux skill (lack?) at the moment. This way, I optimize the distros in the Box, take a "snapshot" like saving a video game, and try out the risky operations. If they fail and I break the distro, I can just open the snapshot up and go back to where I was right before the risky operation.   While this still seems like the best idea so far, I have noticed that the distros I have installed on Virtual Box report that I am NOT using my computer's actual hardware, and am actually using Virtual Box's "hardware", for instance, the "Innotek Systemberatung GmbH VirtualBox Graphics adapter.  Because of that adapter, my test graphics installations do not work properly. Even the operations I know would brick the distro with a black screen are not working. "My adapter is incompatible," FGLRX installation says, in the GUI version of installation (one of many methods).  My questions are: Can I not install these drivers inside of Virtual Box? Do I need some additional software? Is there any other virtual environment I could use for testing these distros that would result in a 100% identical virtual installation?    I am using the notoriously Linux-unfriendly Acer Aspire 5553G, which has "switchable graphics".  Those cards are the Mobility Radeon HD 4250 and 5470. The driver's I have tested so far work in Windows 7, yet do not in Linux.   Thank you all in advance!
120254
I just upgraded from 15.04 to 15.10 and during the boot process I now get an error saying that some modules failed to load. So I ran systemctl status -l systemd-modules-load.service and I got this:  Oct 24 12:22:23 ubuntu systemd-modules-load[292]: Inserted module 'option' Oct 24 12:22:23 ubuntu systemd-modules-load[292]: could not find module by name='off' Oct 24 12:22:23 ubuntu systemd-modules-load[292]: Failed to insert 'off': Function not implemented Oct 24 12:22:23 ubuntu systemd-modules-load[292]: could not find module by name='off' Oct 24 12:22:23 ubuntu systemd-modules-load[292]: Failed to insert 'off': Function not implemented Oct 24 12:22:23 ubuntu systemd-modules-load[292]: Inserted module 'cuse' Oct 24 12:22:23 ubuntu systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Oct 24 12:22:23 ubuntu systemd[1]: Failed to start Load Kernel Modules. Oct 24 12:22:23 ubuntu systemd[1]: systemd-modules-load.service: Unit entered failed state. Oct 24 12:22:23 ubuntu systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.   When I run cat /etc/modules I get  loop lp usbserial option nouveau nouveau   I tried to comment out one of the nouveau modules but it didn't help.  I found a  on Launchpad which gives a similar message but my problem doesn't seem to be caused by the rtc module (which is the culprit in the linked bug).  Anyone has an idea what I should try?  EDIT: added more info:  cat /lib/systemd/system/systemd-modules-load.service gives  [Unit] Description=Load Kernel Modules Documentation=man:systemd-modules-load.service(8) man:modules-load.d(5) DefaultDependencies=no Conflicts=shutdown.target Before=sysinit.target shutdown.target ConditionCapability=CAP_SYS_MODULE ConditionDirectoryNotEmpty=|/lib/modules-load.d ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d ConditionDirectoryNotEmpty=|/etc/modules-load.d ConditionDirectoryNotEmpty=|/run/modules-load.d ConditionKernelCommandLine=|modules-load ConditionKernelCommandLine=|rd.modules-load  [Service] Type=oneshot RemainAfterExit=yes ExecStart=/lib/systemd/systemd-modules-load TimeoutSec=90s   cat /etc/modules-load.d/modules.conf gives the same output as cat /etc/modules/ listed above.
117628
I'm trying to install the Debian ISO, debian-live-7.2-amd64-standard.iso into a virtual machine in VirtualBox but it just hangs.  I'm running this version:  $ virtualbox -h Oracle VM VirtualBox Manager 4.3.6_RPMFusion (C) 2005-2013 Oracle Corporation All rights reserved.
44893
Someone told me that a virtualizing program like VirtualBox does not work like an emulator does in the sense that it doesn't emulate registers and uses the actual ones for the virtualized data that are on the CPU. Emulators must emulate the registers since they are mostly to execute software that depends on a foreign environment (e.g. a Genesis emulator needs Motorola 68000's registers and memory addresses, so developer must make these resources available as emulated registers).  My main question is, how is virtualization developed? How do we enable an entire OS to run as a process in a virtual machine, but get it to run independently while still making use of the actual CPU? I only know emulation, not virtualization, so if anyone could help that'd be nice!  PS: I am not asking solely what the difference is, but differences in how they run software.
30556
I have set up an init-script to control the state of a VirtualBox VM:  #!/bin/sh #chkconfig: 35 99 5 #description: vTiger virtual machine  ### BEGIN INIT INFO # Provides: vtigervm # Required-Start: $local_fs # Requider-Stop: $stop_fs # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Short-Description: Manage vTiger virtual machine # Description: Utility to start and stop vTiger virtual machine on VirtualBox ### END INIT INFO  start() {     echo -n "Starting vTiger"     echo     su myuser -c '/usr/bin/VBoxManage startvm "vTiger" --type headless'     echo "Started virtual machine" &gt;&gt; /var/log/messages }  stop() {     echo -n "Shutting vTiger down..."     echo     su myuser-c '/usr/bin/VBoxManage controlvm "vTiger" acpipowerbutton'     while [ ! -z "`su - juhani -c '/usr/bin/VBoxManage list runningvms | grep vTiger'`" ]; do         echo -n "."         sleep 1     done     echo "Done."     echo "Stopped virtual machine" &gt;&gt; /var/log/messages }  status() {     echo -n "Running VMs: "     su myuser -c '/usr/bin/VBoxManage list runningvms'     echo     if [ -z "`su - juhani -c '/usr/bin/VBoxManage list runningvms | grep vTiger'`" ]; then         RETVAL=3         else         RETVAL=0     fi     echo "Queried virtual machine status" &gt;&gt; /var/log/messages }  echo "Called virtual machine management script with: $1" &gt;&gt; /var/log/messages case "$1" in   start)         start    ;;    stop)         stop    ;;    restart|try-restart|condrestart|reload)         stop         start    ;;    status)         status    ;;    *)         echo $"Usage: $0 {start|stop|restart|status}"         exit 1    ;; esac  exit $RETVAL   The system is CentOS 6.5. If I manually run service [start|stop|status] vtigervm, it works as I expect it to. If the VM is running, $? after the service vtigervm status returns 0, and 3 if it is stopped. I installed it with chkconfig and it created among a few others rc5.d/S99vtigervm and rc0.d/K05vtigervm.  The problem  When I start the system it starts the "service", but on shutdown it does not even run the scripts.  grep "virtual machine" /var/log/messages shows:  *[machine starting]* Called virtual machine management script with: start Started virtual machine *[shutdown -h now]* *[machine stopped]*   What I expect:  *[machine starting]* Called virtual machine management script with: start Started virtual machine  *[shutdown -h now]* Called virtual machine management script with: status Queried virtual machine status Called virtual machine management script with: stop Stopped virtual machine *[machine stopped]*   File permissions &amp; etc:  # ls -lah /etc/rc0.d/ lrwxrwxrwx. 1 root root 13 7.2. 17:49 /etc/rc0.d/K05atd -&gt; ../initd.d/atd lrwxrwxrwx. 1 root root 18 9.2. 00:06 /etc/rc0.d/K05vtigervm -&gt; ../initd.d/vtigervm
92804
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      '/etc/init.d/vboxdrv setup'      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.   This is a familiar message to everyone that uses Virtual Box. This "bug" has been popping up every few months at least since 11.10. I got it today for the first time on 14.04 and unfortunately the  of re-installing virtualbox-dkms is not having any effect:  sudo apt-get install linux-headers-generic build-essential dkms sudo apt-get remove virtualbox-dkms sudo apt-get install virtualbox-dkms   What could be the reason for this old fix to fail?  Update: In the comments user bain makes reference to an old thread that apparently reports to the same problem. While the error message is similar, on Ubuntu 14.04 this issue seems to have a different nature, unrelated to the virtualbox-dkms package. For instance, on Ubuntu 14.04 the virtualbox package is up to date:  $ sudo apt-cache policy virtualbox virtualbox:   Installed: 4.3.10-dfsg-1   Candidate: 4.3.10-dfsg-1   Version table:  *** 4.3.10-dfsg-1 0         500 http://de.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages         100 /var/lib/dpkg/status
81918
Yesterday my Virtualbox guests were still running. Today I get the following error for all guests (windows or Linux).  Failed to open a session for the virtual machine win10.  The VM session was closed before any attempt to power it on.  Result Code: NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}   I already tried to run sudo /sbin/vboxconfig, reinstalling from Software Manager, reinstalling following  and upgrading to 5.2.12 r122591 and 5.2.14 r123301. The result was always the same.  My current kernel version is 4.15.0-24-generic #26-Ubuntu SMP.  $ VBoxManage list extpacks Extension Packs: 1 Pack no. 0:   Oracle VM VirtualBox Extension Pack Version:      5.2.14 Revision:     123301 Edition:       Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe. VRDE Module:  VBoxVRDP Usable:       true
28832
My PC was working yesterday without any problem. I shut it down and tried to open this morning. It prints out these messages on the black screen:  systemd-udevd[713]: failed to execute '/bin/systemctl' '/bin/systemctl start --no-block nvidia-persistenced.service': No such file or directory  systemd-udevd[852]: failed to execute '/bin/systemctl' '/bin/systemctl stop--no-block nvidia-persistenced': No such file or directory   It then continued with the login screen. I entered my password and pressed enter. It waited for a while and the login screen reappeared again.  How can I fix the problem?
124061
I created a virtual machine to install ubuntu 14.04 on VirtualBox 4.2.12.*. I created virtual CD to install it with fixed-size virtual disk of 200GB. After successful installation, it restarted as usual. But after showing message of below, it hangs. Actually, I created virtual machines to install ubuntu at Virtual Box successfully several times. It's very easy. The installed ubuntu versions ranged from 9.10, 13.04 and even 14.04 before. I don't know why this time it hangs at restarting after successful installation. The only difference between this failure restart and previous successful ones is that the virtual disk is much larger, 200GB. It failed three times.  * Deactivating swap... [OK] * Stopping remaining crypto disks... [OK] * Stopping early drypto disks... [OK]
120622
I received the updates through normal Software Updater, 10-Jan-2018. After this VirtualBox would not start any VM, complaining about dkms and asking to make modprobe vboxdrv. Following the advice I reinstalled virtualbox-dkms with:  sudo apt-get --reinstall install virtualbox-dkms   After this and a reboot I tried to start a VM which freezed the whole machine and a hard reboot was necessary.  Is there a way to make VirtualBox work with the latest kernels?  EDIT:  As suggested by N0rbert, the command:  apt-cache policy `dpkg -S VirtualBox | head -n1 | sed -e 's/://g' | awk '{print $1}'`  gives:   virtualbox-qt:   Installed: 5.0.40-dfsg-0ubuntu1.16.04.2   Candidate: 5.0.40-dfsg-0ubuntu1.16.04.2   Version table:  *** 5.0.40-dfsg-0ubuntu1.16.04.2 500         500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages         100 /var/lib/dpkg/status      5.0.18-dfsg-2build1 500         500 http://fr.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages   EDIT (on 29-Mar-2018): Issue is resolved for me, with the Ubuntu Ubdate from today. I have seen that it had some virtualbox-updates, therefore I tried to boot with the most recent kernel again. Then I had to run  sudo apt-get --reinstall install virtualbox-dkms  And after this my virtual machines in VirtualBox started working without crashing the whole computer. Finally!
27665
I'm running the current stable Ubuntu version (Oneiric) but have issues with the shipped kernel. Newer kernel versions seem to have fixed it, but the kernel-ppa/ppa does not contain the most recent kernel which is why I want to install the kernel from the next stable version (Precise). Since I want to be able to unload out of tree kernel modules, the mainline kernel from  cannot be used.  I also have have Virtual Box installed which also need to work in the new kernel so the "kernel headers" have to be upgraded as well.  How am I supposed to install the kernel packages from the next stable version (Precise) without upgrading all other packages?
12326
I am trying to install virtual box v4.3.28-100309 on a Windows 10 Host. The windows 10 insider preview installed is build 10130. When I try to install the virtualbox exe I am getting the following error:  Status: Rolling Back action:    And after this I get a dialog box:  Oracle VM Virtualbox 4.3.28 Setup Wizard ended prematurely    I am running Windows 10 on a i5-core processor with 8GB Ram machine and not a virtual machine.
117505
So I tried to start my apache2 server with the following command...  sudo service apache2 start   But then I get this error message...  Job for apache2.service failed. See "systemctl status apache2.service" and "journalctl -xe" for details.   So when I try and see the systemctl, I get this...  ● apache2.service - LSB: Apache2 web server    Loaded: loaded (/etc/init.d/apache2)    Active: failed (Result: exit-code) since Mon 2015-07-06 10:34:49 IST; 4min 23s ago      Docs: man:systemd-sysv-generator(8)   Process: 8899 ExecStart=/etc/init.d/apache2 start (code=exited, status=2)  Jul 06 10:34:49 archisman-HP-ProBook-440-G2 systemd[1]: Starting LSB: Apache2 web server... Jul 06 10:34:49 archisman-HP-ProBook-440-G2 apache2[8899]: /etc/init.d/apache2: 64: .: Can't open /etc/apache2/envvars Jul 06 10:34:49 archisman-HP-ProBook-440-G2 apache2[8899]: /etc/init.d/apache2: 76: .: Can't open /etc/apache2/envvars Jul 06 10:34:49 archisman-HP-ProBook-440-G2 apache2[8899]: ERROR: APACHE_PID_FILE needs to be defined in /etc/apache2/envvars Jul 06 10:34:49 archisman-HP-ProBook-440-G2 systemd[1]: apache2.service: control process exited, code=exited status=2 Jul 06 10:34:49 archisman-HP-ProBook-440-G2 systemd[1]: Failed to start LSB: Apache2 web server. Jul 06 10:34:49 archisman-HP-ProBook-440-G2 systemd[1]: Unit apache2.service entered failed state. Jul 06 10:34:49 archisman-HP-ProBook-440-G2 systemd[1]: apache2.service failed.    on my browser also gives me an error which means apache is not running.  When I do this...  sudo restart apache2   I get this error...  restart: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused   Somebody please help.
46956
I did upgrade VirtualBox from 4.1 to 4.2  wheneverver I want to load my Win XP VDI, it gives me the following error:     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  /etc/init.d/vboxdrv setup   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.  I ran the suggested step to reinstall the kernel module, and the log file is as follow:  Makefile:181: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=&lt;directory&gt; and run Make again.  Stop. Makefile:181: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=&lt;directory&gt; and run Make again.  Stop. Makefile:181: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=&lt;directory&gt; and run Make again.  Stop.   I still unable to re-run my win virtual XP vdi file.  Anyone have any clue?
10997
I'm running a linux box(ubuntu) and every few months it freezes and I'm left with no choice(SysRq-F and other keyboard shortcuts are not working) but to reboot it losing all the data.   I'm wondering why the kernel is not killing the processe(s) that eats the memory or CPU?   What's the point keeping the system in a frozen/unresponsive state?
12734
When I run sudo service apache2 start I get this error:  Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.   And when I run systemctl status apache2.service I get this:  ● apache2.service - The Apache HTTP Server    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)    Active: failed (Result: exit-code) since Tue 2019-01-15 16:20:26 -03; 7min ago   Process: 8101 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)  ene 15 16:20:26 pc systemd[1]: Starting The Apache HTTP Server... ene 15 16:20:26 pc apachectl[8101]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1.  ene 15 16:20:26 pc apachectl[8101]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for main error log ene 15 16:20:26 pc apachectl[8101]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for error log of vhost  ene 15 16:20:26 pc apachectl[8101]: AH00014: Configuration check failed ene 15 16:20:26 pc apachectl[8101]: Action 'start' failed. ene 15 16:20:26 pc apachectl[8101]: The Apache error log may have more information. ene 15 16:20:26 pc systemd[1]: apache2.service: Control process exited, code=exited status=1 ene 15 16:20:26 pc systemd[1]: apache2.service: Failed with result 'exit-code'. ene 15 16:20:26 pc systemd[1]: Failed to start The Apache HTTP Server.   What can I do about this?