Error module vboxdrv not found

Running the sudo sh vboxsign.sh and getting "FATAL: Module vboxdrv not found in directory /lib/modules/4.10.0-20-generic" What am I missing? This ran fine last time, but I've since upgraded, and m...

Running the sudo sh vboxsign.sh and getting
«FATAL: Module vboxdrv not found in directory /lib/modules/4.10.0-20-generic»

What am I missing? This ran fine last time, but I’ve since upgraded, and must have forgotten something. I set working directory correctly.

asked May 4, 2017 at 23:45

Tom Mercer's user avatar

Try do reinstall «virtualbox-dkms»

sudo apt install --reinstall virtualbox-dkms

answered May 8, 2017 at 0:50

Mariogrip's user avatar

MariogripMariogrip

4444 silver badges4 bronze badges

5

For me, reinstalling virtualbox-dkms always gave an error. It was my first time upgrading the kernel, and hadn’t upgraded the headers. I needed to also do

sudo aptitude install linux-headers-`uname -r`

and not accept it’s first solution (which was to actually do nothing), but accept the second solution which was to upgrade some further library. After that, then

sudo apt install --reinstall virtualbox-dkms

worked for me.

answered Nov 29, 2018 at 18:32

kr37's user avatar

kr37kr37

2012 silver badges3 bronze badges

1

Based on other answers and the Virtualbox official documentation, here is something that worked:

sudo apt-get install build-essential linux-headers-`uname -r`
sudo apt-get install autoconf automake bc bison build-essential flex gcc g++ make python -y
sudo apt-get purge virtualbox

sudo sh -c 'echo "deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian $(lsb_release -c | cut -f2) non-free contrib" >> /etc/apt/sources.list.d/virtualbox.org.list'

wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
sudo apt-get update
sudo apt-get install virtualbox-6.0

blowder's user avatar

answered Nov 12, 2019 at 11:10

psychoslave's user avatar

Reinstallation as mentioned above — had not helped me (within (X)Ubuntu 18.04, with the recently updated kernel).
What worked in my case:

  1. Setup key with:

    wget -q -O - http://download.virtualbox.org/virtualbox/debian/oracle_vbox_2016.asc | sudo apt-key add -
    
  2. Setup repository with:

    sudo sh -c 'echo "deb http://download.virtualbox.org/virtualbox/debian cosmic non-free contrib" >> /etc/apt/sources.list.d/virtualbox.org.list'
    
  3. Download and install the latest version of VirtualBox (with all the extra packages) from this link.

zx485's user avatar

zx485

2,18311 gold badges23 silver badges31 bronze badges

answered Nov 13, 2018 at 21:00

Sergiusz Golec's user avatar

1

i had the same problem after updating Kernel to 5.4.0-37
and i faced some problems worth mentioning:

turns out you can’t install Guest additions using old versions of Virtual-box (i guess any version before 5.2) while using this new kernel and Virtualbox-dkms is not supported anymore.
the only way to solve the problem is to remove old version and install Virtual-box 6 from Oracle but this code:sudo apt-get purge virtualbox leaves some stuff behind.

after using purge to remove Virtualbox, search «virtualbox» in system directory (/) and manually remove everything then install Virtualbox 6 and Guest addition.

that worked for me.

answered Jun 18, 2020 at 9:07

vbeh's user avatar

vbehvbeh

263 bronze badges

I upgraded the system and did

sudo pacman -S virtualbox virtualbox-host-modules virtualbox-guest-iso
virtualbox-host-dkms

yaourt virtualbox-ext-oracle

sudo depmod -a

sudo modprobe vboxdrv

modprobe: FATAL: Module vboxdrv not found.

enter image description here

Community's user avatar

asked May 9, 2015 at 10:01

Lynob's user avatar

The problem was that I followed tutorials on the web and youtube videos, instead of reading manjaro wiki.

The correct way of doing it is not to install virtualbox virtualbox-host-modules, instead of that, first I should check kernel version uname -r in my case I’m using 3.16.7.10-1-MANJARO so I have to do

sudo pacman -S linux316-virtualbox-host-modules

As time goes on, blogs get more and more popular, they get better ranked, leaving official documentation way behind and users like me get false information. Anyway, hopefully my answer helps future users.

answered May 9, 2015 at 17:53

Lynob's user avatar

LynobLynob

4,00412 gold badges42 silver badges72 bronze badges

These are the simplified steps:

The firt step you should be super user.

pacman -S linux-headers
pacman -S virtualbox virtualbox-guest-iso
modprobe vboxdrv

…but if you do not want to do manually at each startup:

open the file

 vim /etc/modules-load.d/virtualbox.conf

add to the current file

vboxdrv

Add usernames to the vboxusers group

gpasswd -a $USER vboxusers

Troubleshooting[/b:8wk2jz3u]

If you put the network adapter in bridged mode

modprobe -a vboxdrv vboxnetadp vboxnetflt

or if you do not want to do manually at each startup:

vim /etc/modules-load.d/virtualbox.conf

vboxnetadp
vboxnetflt

Thanks to hector for the clear and good answer

answered Aug 12, 2016 at 21:43

Michael Horojanski's user avatar

A reboot fixed the problem for me.

The problem was that I’ve updated the kernel and did not reboot since then, so modprobe was still looking in the old path, and obviously could not find the modules it was looking for.

answered Feb 27, 2018 at 15:37

Florian Moser's user avatar

1

Стоит Linux Mint 19.3 Tricia, ядро 5.4.0-37-generic на ноутбуке, в BIOS которого включен UEFI и отключен Secure Boot.
При запуске гостевой операционной системы получаю ошибку, описанную ниже. Перепробовал много разных вариантов которые предлагаю в интернете: откат на ядро 5.0, которое было установлено изначально с Linux, установка / переустановка разных пакетов, модулей — но ничего не помогает.

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up
correctly. Please reinstall virtualbox-dkms package and load the
kernel module by executing

‘modprobe vboxdrv’

as root.

If your system has EFI Secure Boot enabled you may also need to sign
the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before
you can load them. Please see your Linux system’s documentation for
more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) — The
support driver is not installed. On linux, open returned ENOENT.

при команде
modprobe vboxdrv
получаю
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.4.0-37-generic

$ apt install vboxdrv

Чтение списков пакетов…
Готово
Построение дерева зависимостей
Чтение информации о состоянии…
Готово
E: Невозможно найти пакет vboxdrv

и так для всех пакетов: vboxdrv, vboxnetflt, vboxnetadp, vboxpci

Подскажите, что делать чтобы запустить гостевую ОС?

Я использую Oracle VirtualBox для тестирования различных дистрибутивов Linux и Unix.

На данный момент я проверил сотни виртуальных машин в VirtualBox.

Сегодня я запустил серверную виртуальную машину Ubuntu 18.04 на своем рабочем столе Ubuntu 18.04 и получил следующую ошибку.

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 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.

Я нажал «ОК», чтобы закрыть окно сообщения, и увидел еще один момент на заднем плане.

Failed to open a session for the virtual machine Ubuntu 18.04 LTS Server.

The virtual machine 'Ubuntu 18.04 LTS Server' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Я не знал, что делать в первую очередь.

Я запустил следующую команду, чтобы проверить, поможет ли это.

$ sudo modprobe vboxdrv

И я получил эту ошибку.

modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.0.0-23-generic

Внимательно прочитав оба сообщения об ошибках, я понял, что должен обновить приложение Virtualbox.

Если вы когда-нибудь сталкивались с этой ошибкой в Ubuntu и ее вариантах, таких как Linux Mint, все, что вам нужно сделать, это просто переустановить или обновить пакет «virtualbox-dkms» с помощью команды:

$ sudo apt install virtualbox-dkms

Или гораздо лучше обновить всю систему:

$ sudo apt upgrade

Теперь ошибка исчезла, и я мог без проблем запускать виртуальные машины из VirtualBox.

I am using linux-lts44 from AUR. And both linux and linux-headers are installed:

$ sudo pacman -Q linux-lts44
linux-lts44 4.4.168-1

$ sudo pacman -Q linux-lts44-headers
linux-lts44-headers 4.4.168-1

but when I load the module manually, I get this error:

$ sudo modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.4.168-1-lts4

I found this same issue [SOLVED] VirtualBox: modprobe vboxdrv failure and solution was to install virtualbox-host-dkms, but I’m getting Error! Bad return status for module build on kernel: 4.4.168-1-lts44 (x86_64)

$ sudo pacman -S virtualbox-host-dkms
warning: virtualbox-host-dkms-5.2.22-1 is up to date — reinstalling
resolving dependencies…
looking for conflicting packages…

Packages (1) virtualbox-host-dkms-5.2.22-1

Total Installed Size:  11.56 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                                         [############################################################] 100%
(1/1) checking package integrity                                                                       [############################################################] 100%
(1/1) loading package files                                                                            [############################################################] 100%
(1/1) checking for file conflicts                                                                      [############################################################] 100%
(1/1) checking available disk space                                                                    [############################################################] 100%
:: Running pre-transaction hooks…
(1/1) Remove DKMS modules
:: Processing package changes…
(1/1) reinstalling virtualbox-host-dkms                                                                [############################################################] 100%
:: Running post-transaction hooks…
(1/2) Install DKMS modules
==> dkms install vboxhost/5.2.22_OSE -k 4.4.168-1-lts44
Error! Bad return status for module build on kernel: 4.4.168-1-lts44 (x86_64)
Consult /var/lib/dkms/vboxhost/5.2.22_OSE/build/make.log for more information.
(2/2) Arming ConditionNeedsUpdate…

contents of /var/lib/dkms/vboxhost/5.2.22_OSE/build/make.log:

$ cat /var/lib/dkms/vboxhost/5.2.22_OSE/build/make.log
DKMS make.log for vboxhost-5.2.22_OSE for kernel 4.4.168-1-lts44 (x86_64)
Wed Dec 19 21:38:52 PST 2018
make: Entering directory ‘/usr/lib/modules/4.4.168-1-lts44/build’
  LD      /var/lib/dkms/vboxhost/5.2.22_OSE/build/built-in.o
  LD      /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/built-in.o
  LD      /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/built-in.o
  LD      /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/built-in.o
  LD      /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/built-in.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/linux/VBoxPci-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/VBoxNetAdp.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/VBoxPci.o
  LD [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetadp/vboxnetadp.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/SUPR0IdcClient.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/linux/SUPR0IdcClient-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/SUPR0IdcClient.o
  LD [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxpci/vboxpci.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrvGip.o
  LD [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxnetflt/vboxnetflt.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeLockUser’:
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1122:33: warning: passing argument 6 of ‘get_user_pages’ makes pointer from integer without a cast [-Wint-conversion]
                                 fWrite,                 /* force write access. */
                                 ^~~~~~
In file included from /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98,
                 from /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
include/linux/mm.h:1202:45: note: expected ‘struct page **’ but argument is of type ‘int’
       unsigned int gup_flags, struct page **pages,
                               ~~~~~~~~~~~~~~^~~~~
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1124:33: warning: passing argument 7 of ‘get_user_pages’ from incompatible pointer type [-Wincompatible-pointer-types]
                                 &pMemLnx->apPages[0],   /* Page array. */
                                 ^~~~~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98,
                 from /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
include/linux/mm.h:1203:31: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’
       struct vm_area_struct **vmas);
       ~~~~~~~~~~~~~~~~~~~~~~~~^~~~
/var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1112:18: error: too many arguments to function ‘get_user_pages’
             rc = get_user_pages(pTask,                  /* Task for fault accounting. */
                  ^~~~~~~~~~~~~~
In file included from /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98,
                 from /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
include/linux/mm.h:1200:6: note: declared here
long get_user_pages(struct task_struct *tsk, struct mm_struct *mm,
      ^~~~~~~~~~~~~~
  CC [M]  /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o
make[2]: *** [scripts/Makefile.build:277: /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs….
make[1]: *** [scripts/Makefile.build:484: /var/lib/dkms/vboxhost/5.2.22_OSE/build/vboxdrv] Error 2
make: *** [Makefile:1436: _module_/var/lib/dkms/vboxhost/5.2.22_OSE/build] Error 2
make: Leaving directory ‘/usr/lib/modules/4.4.168-1-lts44/build’

What should I do next?

UPDATE:
Problem solved by modifying get_user_pages from /usr/lib/modules/4.4.168-1-lts44/build/include/linux/mm.h

long get_user_pages(struct task_struct *tsk, struct mm_struct *mm,
            unsigned long start, unsigned long nr_pages,
            int write, int force, struct page **pages,
            struct vm_area_struct **vmas);

You will get another error «libQt5Core.so.5: cannot open shared object file: No such file or directory» when running virtualbox because qt5.12 has problems running on kernels below 4.11. To fix this, remove qt5-base and replace wit qt5-base-nostatx from AUR.

Last edited by b3n10 (2018-12-20 01:59:22)

I use Oracle VirtualBox to test various Linux and Unix distributions. I’ve tested so many virtual machines in VirtualBox. Today, I started Ubuntu 18.04 server VM in my Ubuntu 18.04 desktop and I encountered with 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 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.

Kernel driver not installed (rc=-1908) virtualbox ubuntu

«Kernel driver not installed (rc=-1908)» Error in Ubuntu

I clicked OK to close the message box and and I saw another one in the background.

Failed to open a session for the virtual machine Ubuntu 18.04 LTS Server.

The virtual machine 'Ubuntu 18.04 LTS Server' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

The virtual machine Ubuntu has terminated unexpectedly during startup with exit code 1 (0x1)

The virtual machine has terminated unexpectedly during startup with exit code 1 (0x1)

I didn’t know what to do first. So, I ran the following command to check if it helps.

$ sudo modprobe vboxdrv

And, I got this error:

modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.0.0-23-generic

After carefully reading the both error messages, I realized that I should update the Virtualbox application.

If you ever run into this error in Ubuntu and its variants like Linux Mint, all you have to do is just reinstall or update the «virtualbox-dkms» package using command:

$ sudo apt install virtualbox-dkms

Or, it is much better to update the whole system:

$ sudo apt upgrade

Now the error has gone and I could start VMs from VirtualBox without any issues.

Related read:

  • Solve «Cannot change group vboxusers for device /dev/vboxdrv» Virtualbox Error
  • Solve “Result Code: NS_ERROR_FAILURE (0x80004005)” VirtualBox Error In Arch Linux

16 comments

Concerned User
October 23, 2019 — 8:02 pm

Thanks. This worked for me on Ubuntu 19.10.


Reply

Paulo
November 27, 2019 — 1:07 am

Thank you very much! Worked like a charm on Ubuntu 19.10!


Reply

Yuval Benzuk
January 23, 2020 — 3:20 pm

Thank you for the easy solution!


Reply

Guido
February 1, 2020 — 9:24 pm

With Kernel 5.2+ install gcc-8 before installing virtualbox.

Ubuntu 18.04.x comes with gcc-7.x.
The newer kernels are build with gcc-9 and use some instructions that are not available with gcc-7.


Reply

Shalinda Fernando
July 7, 2020 — 4:17 pm

For me it worked after I rebooted my machine


Reply

Pete
July 20, 2020 — 1:31 am

It didn’t work on Linux Mint 20. The error stayed the same even after the reboot :/


Reply

matias
July 20, 2020 — 12:57 pm


Reply

jessica
August 10, 2020 — 6:09 pm

for me too! can’t find my way over this error >.<


Reply

vedvarshith
October 2, 2020 — 12:05 pm

thanks but if i doesn’t start enable virtualization in the BIOS


Reply

Amir fakoor
November 14, 2020 — 4:16 pm

Thank you, This worked for me on Ubuntu 20.10


Reply

Thomas Blackk
August 6, 2021 — 2:20 pm

thanks worked on ubuntu (reboot was required)


Reply

sk
August 6, 2021 — 5:35 pm

Glad I could help.


Reply

Jake
October 31, 2021 — 3:44 am

Didn’t work. Output here:

sudo apt install virtualbox-dkms
Reading package lists… Done
Building dependency tree
Reading state information… Done
You might want to run ‘apt –fix-broken install’ to correct these.
The following packages have unmet dependencies:
systemd-timesyncd : Depends: systemd (= 245.4-4ubuntu3.6)
E: Unmet dependencies. Try ‘apt –fix-broken install’ with no packages (or specify a solution).


Reply

sk
October 31, 2021 — 11:05 am

Have you tried this command?

sudo apt --fix-broken install


Reply

Eswar
November 3, 2021 — 4:03 pm

I am facing same issue but didn’t get resolved. I am using Ubuntu 20


Reply

AD
February 28, 2022 — 11:08 am

Thank you it`s solve my problem


Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Hello everybody!

Today I started using Linux Ubuntu, I am a total newbie…

I would to like to install a second OS, inside Ubuntu.

I heard of VirtualBox, it sounds great!

But I have some problems whille trying to boot up the setup inside VirtualBox.

I get this error message from VirtualBox;

VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Please install the virtualbox-ose-modules package for your kernel and execute ‘/etc/init.d/vboxdrv start’ as root.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).

Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

«Please install the virtualbox-ose-modules package for your kernel and execute ‘/etc/init.d/vboxdrv start’ as root.»

So, I installed the virtualbox-ose-modules that with synaptic packet manager.

After that, I run ‘/etc/init.d/vboxdrv start’

Then I got this message;

/etc/init.d/vboxdrv start
open: Permission denied
* Starting VirtualBox kernel module vboxdrv FATAL: Module vboxdrv not found.

open: Permission denied
* Modprobe vboxdrv failed. Please use ‘dmesg’ to find out why.

After entering ‘dmesg’ in the kernel, I got this info;

[ 0.000000] Linux version 2.6.22-14-server (buildd@palmer) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:34:23 GMT 2007 (Ubuntu 2.6.22-14.46-server)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 — 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 — 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 — 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 — 000000002ffec000 (usable)
[ 0.000000] BIOS-e820: 000000002ffec000 — 000000002ffef000 (ACPI data)
[ 0.000000] BIOS-e820: 000000002ffef000 — 000000002ffff000 (reserved)
[ 0.000000] BIOS-e820: 000000002ffff000 — 0000000030000000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000fec00000 — 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 — 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffff0000 — 0000000100000000 (reserved)
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 767MB LOWMEM available.
[ 0.000000] Entering add_active_range(0, 0, 196588) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 196588
[ 0.000000] HighMem 196588 -> 196588
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 196588
[ 0.000000] On node 0 totalpages: 196588
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1503 pages used for memmap
[ 0.000000] Normal zone: 190989 pages, LIFO batch:31
[ 0.000000] HighMem zone: 0 pages used for memmap
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: RSDP signature @ 0xC00F5270 checksum 0
[ 0.000000] ACPI: RSDP 000F5270, 0014 (r0 ASUS )
[ 0.000000] ACPI: RSDT 2FFEC000, 0030 (r1 ASUS P4B533 42302E31 MSFT 31313031)
[ 0.000000] ACPI: FACP 2FFEC0C0, 0074 (r1 ASUS P4B533 42302E31 MSFT 31313031)
[ 0.000000] ACPI: DSDT 2FFEC134, 2816 (r1 ASUS P4B533 1000 MSFT 100000B)
[ 0.000000] ACPI: FACS 2FFFF000, 0040
[ 0.000000] ACPI: BOOT 2FFEC030, 0028 (r1 ASUS P4B533 42302E31 MSFT 31313031)
[ 0.000000] ACPI: APIC 2FFEC058, 005A (r1 ASUS P4B533 42302E31 MSFT 31313031)
[ 0.000000] ACPI: PM-Timer IO Port: 0xe408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] Processor #0 15:2 APIC version 20
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 22 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
[ 0.000000] Built 1 zonelists. Total pages: 195053
[ 0.000000] Kernel command line: root=UUID=d1cde149-9b6b-4437-a6f1-cbc6ba50695f ro quiet splash
[ 0.000000] mapped APIC to ffffd000 (fee00000)
[ 0.000000] mapped IOAPIC to ffffc000 (fec00000)
[ 0.000000] Enabling fast FPU save and restore… done.
[ 0.000000] Enabling unmasked SIMD FPU exception support… done.
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[ 0.000000] Detected 2019.988 MHz processor.
[ 20.974257] Console: colour VGA+ 80×25
[ 20.975236] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 20.976250] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 21.002261] Memory: 768104k/786352k available (2047k kernel code, 17592k reserved, 920k data, 364k init, 0k highmem)
[ 21.002275] virtual kernel memory layout:
[ 21.002276] fixmap : 0xfff4e000 — 0xfffff000 ( 708 kB)
[ 21.002278] pkmap : 0xffc00000 — 0xffe00000 (2048 kB)
[ 21.002279] vmalloc : 0xf0800000 — 0xffbfe000 ( 243 MB)
[ 21.002281] lowmem : 0xc0000000 — 0xeffec000 ( 767 MB)
[ 21.002282] .init : 0xc03eb000 — 0xc0446000 ( 364 kB)
[ 21.002284] .data : 0xc02ffcc6 — 0xc03e5f04 ( 920 kB)
[ 21.002285] .text : 0xc0100000 — 0xc02ffcc6 (2047 kB)
[ 21.002290] Checking if this processor honours the WP bit even in supervisor mode… Ok.
[ 21.002340] SLUB: Genslabs=22, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
[ 21.152085] Calibrating delay using timer specific routine.. 4042.98 BogoMIPS (lpj=20214948)
[ 21.152119] Security Framework v1.0.0 initialized
[ 21.152128] SELinux: Disabled at boot.
[ 21.152145] Mount-cache hash table entries: 512
[ 21.152331] CPU: After generic identify, caps: 3febfbff 00000000 00000000 00000000 00000000 00000000 00000000
[ 21.152347] CPU: Trace cache: 12K uops, L1 D cache: 8K
[ 21.152351] CPU: L2 cache: 512K
[ 21.152355] CPU: Hyper-Threading is disabled
[ 21.152358] CPU: After all inits, caps: 3febfbff 00000000 00000000 0000b080 00000000 00000000 00000000
[ 21.152374] Compat vDSO mapped to ffffe000.
[ 21.152391] Checking ‘hlt’ instruction… OK.
[ 21.192201] SMP alternatives: switching to UP code
[ 21.192491] Freeing SMP alternatives: 11k freed
[ 21.192993] Early unpacking initramfs… done
[ 21.607257] ACPI: Core revision 20070126
[ 21.607328] ACPI: Looking for DSDT in initramfs… error, file /DSDT.aml not found.
[ 21.608836] CPU0: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 04
[ 21.608890] Total of 1 processors activated (4042.98 BogoMIPS).
[ 21.609035] ENABLING IO-APIC IRQs
[ 21.609234] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 21.820897] Brought up 1 CPUs
[ 21.821067] Booting paravirtualized kernel on bare hardware
[ 21.821148] Time: 21:55:26 Date: 10/13/107
[ 21.821180] NET: Registered protocol family 16
[ 21.821312] EISA bus registered
[ 21.821330] ACPI: bus type pci registered
[ 21.823199] PCI: PCI BIOS revision 2.10 entry at 0xf1ea0, last bus=2
[ 21.823202] PCI: Using configuration type 1
[ 21.823204] Setting up standard PCI resources
[ 21.834880] ACPI: EC: Look up EC in DSDT
[ 21.841566] ACPI: Interpreter enabled
[ 21.841571] ACPI: (supports S0 S1 S4 S5)
[ 21.841593] ACPI: Using IOAPIC for interrupt routing
[ 21.848462] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 21.848481] PCI: Probing PCI hardware (bus 00)
[ 21.848952] * The chipset may have PM-Timer Bug. Due to workarounds for a bug,
[ 21.848955] * this clock source is slow. If you are sure your timer does not have
[ 21.848957] * this bug, please use «acpi_pm_good» to disable the workaround
[ 21.849010] PCI: Enabled i801 SMBus device
[ 21.849019] PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO
[ 21.849024] PCI quirk: region ec00-ec3f claimed by ICH4 GPIO
[ 21.849650] PCI: Transparent bridge — 0000:00:1e.0
[ 21.849683] ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT]
[ 21.849789] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PCI1._PRT]
[ 21.849861] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PCI2._PRT]
[ 21.851693] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[ 21.851793] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 21.851906] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[ 21.852016] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 *4 5 6 7 9 10 11 12 14 15)
[ 21.852111] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 21.852208] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 21.852304] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 21.852400] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 21.852517] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 21.852534] pnp: PnP ACPI init
[ 21.852548] ACPI: bus type pnp registered
[ 21.856731] pnp: PnP ACPI: found 12 devices
[ 21.856735] ACPI: ACPI bus type pnp unregistered
[ 21.856741] PnPBIOS: Disabled by ACPI PNP
[ 21.856818] PCI: Using ACPI for IRQ routing
[ 21.856821] PCI: If a device doesn’t work, try «pci=routeirq». If it helps, post a report
[ 21.866327] NET: Registered protocol family 8
[ 21.866330] NET: Registered protocol family 20
[ 21.866344] NetLabel: Initializing
[ 21.866347] NetLabel: domain hash size = 128
[ 21.866349] NetLabel: protocols = UNLABELED CIPSOv4
[ 21.866368] NetLabel: unlabeled traffic allowed by default
[ 21.866460] pnp: 00:00: iomem range 0x0-0x9ffff could not be reserved
[ 21.866464] pnp: 00:00: iomem range 0xf0000-0xfffff could not be reserved
[ 21.866468] pnp: 00:00: iomem range 0x100000-0x2fffffff could not be reserved
[ 21.866472] pnp: 00:00: iomem range 0xfec00000-0xfec000ff could not be reserved
[ 21.866482] pnp: 00:02: ioport range 0xe400-0xe47f has been reserved
[ 21.866486] pnp: 00:02: ioport range 0xe800-0xe81f has been reserved
[ 21.866490] pnp: 00:02: ioport range 0xec00-0xec3f has been reserved
[ 21.866494] pnp: 00:02: ioport range 0x4d6-0x4d6 has been reserved
[ 21.866498] pnp: 00:02: iomem range 0xfff80000-0xffffffff could not be reserved
[ 21.866503] pnp: 00:02: iomem range 0xffb80000-0xffbfffff has been reserved
[ 21.866519] pnp: 00:0b: ioport range 0x3f0-0x3f1 has been reserved
[ 21.870755] Time: tsc clocksource has been installed.
[ 21.896911] PCI: Bridge: 0000:00:01.0
[ 21.896914] IO window: disabled.
[ 21.896920] MEM window: ed000000-ee7fffff
[ 21.896924] PREFETCH window: eff00000-f7ffffff
[ 21.896932] PCI: Bridge: 0000:00:1e.0
[ 21.896936] IO window: b000-bfff
[ 21.896943] MEM window: ec000000-ec7fffff
[ 21.896948] PREFETCH window: ee800000-efefffff
[ 21.896969] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[ 21.896987] NET: Registered protocol family 2
[ 21.990597] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 21.990834] TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
[ 21.993245] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 21.994192] TCP: Hash tables configured (established 131072 bind 65536)
[ 21.994198] TCP reno registered
[ 22.020718] checking if image is initramfs…<6>Switched to high resolution mode on CPU 0
[ 22.412128] it is
[ 22.839025] Freeing initrd memory: 6738k freed
[ 22.839211] Simple Boot Flag at 0x3a set to 0x1
[ 22.839549] audit: initializing netlink socket (disabled)
[ 22.839571] audit(1194990926.260:1): initialized
[ 22.842527] VFS: Disk quotas dquot_6.5.1
[ 22.842606] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 22.842760] io scheduler noop registered
[ 22.842764] io scheduler anticipatory registered
[ 22.842769] io scheduler deadline registered (default)
[ 22.842793] io scheduler cfq registered
[ 22.842865] Boot video device is 0000:01:00.0
[ 22.843082] isapnp: Scanning for PnP cards…
[ 23.199387] isapnp: No Plug & Play device found
[ 23.236280] Real Time Clock Driver v1.12ac
[ 23.236408] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
[ 23.238161] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
[ 23.238469] input: Macintosh mouse button emulation as /class/input/input0
[ 23.238580] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 23.238585] PNP: PS/2 controller doesn’t have AUX irq; using default 12
[ 23.242339] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 23.242349] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 23.242638] mice: PS/2 mouse device common for all mice
[ 23.242793] EISA: Probing bus 0 at eisa.0
[ 23.242840] EISA: Detected 0 cards.
[ 23.242989] TCP cubic registered
[ 23.243004] NET: Registered protocol family 1
[ 23.243038] Using IPI No-Shortcut mode
[ 23.243258] Magic number: 15:127:955
[ 23.243394] hash matches device ptyzc
[ 23.244065] Freeing unused kernel memory: 364k freed
[ 23.278282] input: AT Translated Set 2 keyboard as /class/input/input1
[ 24.574589] fuse init (API version 7.8 )
[ 24.582736] Capability LSM initialized
[ 24.595865] ACPI: Invalid PBLK length [5]
[ 24.595915] ACPI Exception (processor_core-0783): AE_NOT_FOUND, Processor Device is not present [20070126]
[ 25.421736] usbcore: registered new interface driver usbfs
[ 25.421773] usbcore: registered new interface driver hub
[ 25.421805] usbcore: registered new device driver usb
[ 25.423198] USB Universal Host Controller Interface driver v3.0
[ 25.423293] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 25.423310] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[ 25.423315] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 25.423526] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 25.423560] uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000d800
[ 25.423730] usb usb1: configuration #1 chosen from 1 choice
[ 25.423777] hub 1-0:1.0: USB hub found
[ 25.423789] hub 1-0:1.0: 2 ports detected
[ 25.524177] ACPI: PCI Interrupt 0000:00:1d.1[b] -> GSI 19 (level, low) -> IRQ 17
[ 25.524194] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[ 25.524200] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 25.524236] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[ 25.524269] uhci_hcd 0000:00:1d.1: irq 17, io base 0x0000d400
[ 25.524404] usb usb2: configuration #1 chosen from 1 choice
[ 25.524444] hub 2-0:1.0: USB hub found
[ 25.524455] hub 2-0:1.0: 2 ports detected
[ 25.609077] SCSI subsystem initialized
[ 25.617220] libata version 2.21 loaded.
[ 25.634018] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
[ 25.634036] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[ 25.634041] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 25.634075] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[ 25.634107] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d000
[ 25.634245] usb usb3: configuration #1 chosen from 1 choice
[ 25.634286] hub 3-0:1.0: USB hub found
[ 25.634299] hub 3-0:1.0: 2 ports detected
[ 25.743844] PCI: Enabling device 0000:00:1d.7 (0004 -> 0006)
[ 25.743862] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 19
[ 25.743882] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[ 25.743887] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 25.743922] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
[ 25.743973] ehci_hcd 0000:00:1d.7: debug port 1
[ 25.743981] PCI: cache line size of 128 is not supported by device 0000:00:1d.7
[ 25.743995] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xec800000
[ 25.751418] Floppy drive(s): fd0 is 1.44M
[ 25.791670] FDC 0 is a post-1991 82077
[ 25.803521] usb 1-2: new low speed USB device using uhci_hcd and address 2
[ 25.803548] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 25.803741] usb usb4: configuration #1 chosen from 1 choice
[ 25.803787] hub 4-0:1.0: USB hub found
[ 25.803800] hub 4-0:1.0: 6 ports detected
[ 25.913781] PCI: Enabling device 0000:02:0b.0 (0014 -> 0017)
[ 25.913794] ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 23 (level, low) -> IRQ 19
[ 25.913805] 3c59x: Donald Becker and others.
[ 25.913813] 0000:02:0b.0: 3Com PCI 3c980C Python-T at f0806000.
[ 25.937862] ata_piix 0000:00:1f.1: version 2.11
[ 25.937892] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
[ 25.937959] PCI: Setting latency timer of device 0000:00:1f.1 to 64
[ 25.938100] scsi0 : ata_piix
[ 25.938492] scsi1 : ata_piix
[ 25.938655] ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14
[ 25.938661] ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15
[ 26.149569] ata1.01: ATA-7: MAXTOR STM3320820A, 3.AAE, max UDMA/100
[ 26.149576] ata1.01: 625142448 sectors, multi 16: LBA48
[ 26.232534] ata1.01: configured for UDMA/100
[ 26.532103] usb 4-4: new high speed USB device using ehci_hcd and address 3
[ 26.684229] usb 4-4: configuration #1 chosen from 1 choice
[ 26.851803] ata2.00: ATAPI: _NEC DVD_RW ND-2510A, 2.15, max UDMA/33
[ 26.851813] ata2.01: ATAPI: AOPEN DVD1648/LKY, DSA4, max UDMA/33
[ 26.961301] usb 1-2: new low speed USB device using uhci_hcd and address 3
[ 27.051430] ata2.00: configured for UDMA/33
[ 27.142185] usb 1-2: configuration #1 chosen from 1 choice
[ 27.146193] usbcore: registered new interface driver libusual
[ 27.158695] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 27.158703] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 27.162495] Initializing USB Mass Storage driver…
[ 27.162608] scsi2 : SCSI emulation for USB Mass Storage devices
[ 27.162693] usbcore: registered new interface driver usb-storage
[ 27.162697] USB Mass Storage support registered.
[ 27.162713] usb-storage: device found at 3
[ 27.162716] usb-storage: waiting for device to settle before scanning
[ 27.181591] usbcore: registered new interface driver hiddev
[ 27.195273] input: Trust GM-4200 Gamer Optical Mouse as /class/input/input2
[ 27.195307] input: USB HID v1.11 Mouse [Trust GM-4200 Gamer Optical Mouse] on usb-0000:00:1d.0-2
[ 27.195327] usbcore: registered new interface driver usbhid
[ 27.195332] /build/buildd/linux-source-2.6.22-2.6.22/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[ 27.211193] ata2.01: configured for UDMA/33
[ 27.213221] scsi 0:0:1:0: Direct-Access ATA MAXTOR STM332082 3.AA PQ: 0 ANSI: 5
[ 27.214383] scsi 1:0:0:0: CD-ROM _NEC DVD_RW ND-2510A 2.15 PQ: 0 ANSI: 5
[ 27.214767] scsi 1:0:1:0: CD-ROM AOPEN DVD1648/LKY DSA4 PQ: 0 ANSI: 5
[ 27.235682] sd 0:0:1:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
[ 27.235723] sd 0:0:1:0: [sda] Write Protect is off
[ 27.235727] sd 0:0:1:0: [sda] Mode Sense: 00 3a 00 00
[ 27.235777] sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 27.235865] sd 0:0:1:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
[ 27.235879] sd 0:0:1:0: [sda] Write Protect is off
[ 27.235883] sd 0:0:1:0: [sda] Mode Sense: 00 3a 00 00
[ 27.235906] sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 27.235912] sda: sda1 sda2 < sda5 >
[ 27.283741] sd 0:0:1:0: [sda] Attached SCSI disk
[ 27.292647] sd 0:0:1:0: Attached scsi generic sg0 type 0
[ 27.292702] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 27.292729] scsi 1:0:1:0: Attached scsi generic sg2 type 5
[ 27.314291] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
[ 27.314299] Uniform CD-ROM driver Revision: 3.20
[ 27.314380] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 27.325235] sr1: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
[ 27.325320] sr 1:0:1:0: Attached scsi CD-ROM sr1
[ 27.589610] Attempting manual resume
[ 27.589616] swsusp: Resume From Partition 8:5
[ 27.589618] PM: Checking swsusp image.
[ 27.589842] PM: Resume from disk failed.
[ 27.645446] kjournald starting. Commit interval 5 seconds
[ 27.645462] EXT3-fs: mounted filesystem with ordered data mode.
[ 32.151856] usb-storage: device scan complete
[ 32.152481] scsi 2:0:0:0: Direct-Access EM640AA MP3 Player PQ: 0 ANSI: 0 CCS
[ 32.153695] sd 2:0:0:0: [sdb] 4036608 512-byte hardware sectors (2067 MB)
[ 32.154317] sd 2:0:0:0: [sdb] Write Protect is off
[ 32.154321] sd 2:0:0:0: [sdb] Mode Sense: 3b 00 00 00
[ 32.154324] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 32.156438] sd 2:0:0:0: [sdb] 4036608 512-byte hardware sectors (2067 MB)
[ 32.157061] sd 2:0:0:0: [sdb] Write Protect is off
[ 32.157064] sd 2:0:0:0: [sdb] Mode Sense: 3b 00 00 00
[ 32.157067] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 32.157072] sdb: sdb1
[ 32.158138] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 32.158191] sd 2:0:0:0: Attached scsi generic sg3 type 0
[ 34.855923] Linux agpgart interface v0.102 (c) Dave Jones
[ 35.027511] agpgart: Detected an Intel 845G Chipset.
[ 35.031301] agpgart: AGP aperture is 64M @ 0xf8000000
[ 35.039362] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 35.041875] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 35.758730] intel_rng: FWH not detected
[ 36.120206] Linux video capture interface: v2.00
[ 36.160814] input: PC Speaker as /class/input/input3
[ 36.175979] iTCO_vendor_support: vendor-support=0
[ 36.177571] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
[ 36.234448] iTCO_wdt: Found a ICH4 TCO device (Version=1, TCOBASE=0xe460)
[ 36.234502] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 36.253935] parport_pc 00:09: reported by Plug and Play ACPI
[ 36.253993] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
[ 36.585278] bttv: driver version 0.9.17 loaded
[ 36.585285] bttv: using 8 buffers with 2080k (520 pages) each for capture
[ 36.585347] bttv: Bt8xx card found (0).
[ 36.585373] PCI: Enabling device 0000:02:0c.0 (0004 -> 0006)
[ 36.585389] ACPI: PCI Interrupt 0000:02:0c.0[A] -> GSI 20 (level, low) -> IRQ 20
[ 36.585405] bttv0: Bt878 (rev 17) at 0000:02:0c.0, irq: 20, latency: 32, mmio: 0xef000000
[ 36.585438] bttv0: detected: Pinnacle PCTV [card=39], PCI subsystem ID is 11bd:0012
[ 36.585442] bttv0: using: Pinnacle PCTV Studio/Rave [card=39,autodetected]
[ 36.585479] bttv0: gpio: en=00000000, out=00000000 in=00fffbff [init]
[ 36.585858] bttv0: i2c: checking for MSP34xx @ 0x80… found
[ 36.586129] bttv0: pinnacle/mt: id=2 info=»PAL+SECAM / stereo» radio=yes
[ 36.586132] bttv0: using tuner=33
[ 36.586136] bttv0: i2c: checking for MSP34xx @ 0x80… found
[ 36.606057] msp3400 0-0040: MSP3410G-B11 found @ 0x80 (bt878 #0 [sw])
[ 36.606062] msp3400 0-0040: MSP3410G-B11 supports nicam and radio, mode is autodetect and autoselect
[ 36.945903] bttv0: i2c: checking for TDA9875 @ 0xb0… not found
[ 37.078582] bttv0: i2c: checking for TDA7432 @ 0x8a… not found
[ 37.123137] tuner 0-004b: chip found @ 0x96 (bt878 #0 [sw])
[ 37.123190] tda9887 0-004b: tda988[5/6/7] found @ 0x4b (tuner)
[ 37.124328] tuner 0-0060: Chip ID is not zero. It is not a TEA5767
[ 37.124331] tuner 0-0060: chip found @ 0xc0 (bt878 #0 [sw])
[ 37.127279] tuner 0-0060: microtune: companycode=3cbf part=42 rev=22
[ 37.128596] tuner 0-0060: microtune MT2050 found, OK
[ 37.131531] tuner 0-0060: microtune: companycode=3cbf part=42 rev=22
[ 37.132849] tuner 0-0060: microtune MT2050 found, OK
[ 37.145735] bttv0: registered device video0
[ 37.145761] bttv0: registered device vbi0
[ 37.145784] bttv0: registered device radio0
[ 37.163970] bttv0: PLL: 28636363 => 35468950 .. ok
[ 37.215526] PCI: Enabling device 0000:02:03.0 (0084 -> 0085)
[ 37.215543] ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 21 (level, low) -> IRQ 21
[ 37.225636] bt878: AUDIO driver version 0.0.0 loaded
[ 37.225675] bt878: Bt878 AUDIO function found (0).
[ 37.225697] PCI: Enabling device 0000:02:0c.1 (0004 -> 0006)
[ 37.225707] ACPI: PCI Interrupt 0000:02:0c.1[A] -> GSI 20 (level, low) -> IRQ 20
[ 37.225716] bt878_probe: card id=[0x1211bd], Unknown card.
[ 37.225718] Exiting..
[ 37.225723] ACPI: PCI interrupt for device 0000:02:0c.1 disabled
[ 37.225729] bt878: probe of 0000:02:0c.1 failed with error -22
[ 37.603773] lp0: using parport0 (interrupt-driven).
[ 37.652130] Adding 2265124k swap on /dev/sda5. Priority:-1 extents:1 across:2265124k
[ 38.012444] EXT3 FS on sda1, internal journal
[ 39.013025] No dock devices found.
[ 39.074068] input: Power Button (FF) as /class/input/input4
[ 39.074103] ACPI: Power Button (FF) [PWRF]
[ 39.074158] input: Power Button (CM) as /class/input/input5
[ 39.074180] ACPI: Power Button (CM) [PWRB]
[ 41.219341] eth0: setting full-duplex.
[ 41.361761] ppdev: user-space parallel port driver
[ 41.626119] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
[ 41.626127] apm: overridden by ACPI.
[ 42.020552] Capability LSM initialized
[ 42.243804] Bluetooth: Core ver 2.11
[ 42.243894] NET: Registered protocol family 31
[ 42.243897] Bluetooth: HCI device and connection manager initialized
[ 42.243902] Bluetooth: HCI socket layer initialized
[ 42.262018] Bluetooth: L2CAP ver 2.8
[ 42.262024] Bluetooth: L2CAP socket layer initialized
[ 42.340552] Bluetooth: RFCOMM socket layer initialized
[ 42.340572] Bluetooth: RFCOMM TTY layer initialized
[ 42.340575] Bluetooth: RFCOMM ver 1.8
[ 46.625630] NET: Registered protocol family 17
[ 52.176442] NET: Registered protocol family 10
[ 52.176557] lo: Disabled Privacy Extensions
[ 62.969400] eth0: no IPv6 routers present

Does anyone have any idea what I am doing wrong???

Greetings,

MrNewbie

Содержание

Введение
your current centos software installation requires of available space
(rc=-1908) Kernel driver not installed
This system is currently not set up to build kernel modules
(rc=-1912) The VirtualBox kernel modules do not match this version of VirtualBox
Nonexistent host networking interface
Cannot unregister the machine

Возможные проблемы

Если что-то не получилось, особенно в самом начале, например возникла ошибка 1908

Установка Virtual Windows 7 на Debian Linux изображение с сайта www.andreyolegovich.ru

rc=-1908


wwww.andreyolegovich.ru

и

Установка Virtual Windows 7 на Debian Linux изображение с сайта www.andreyolegovich.ru

rc=-1908


wwww.andreyolegovich.ru

Советую подумать:

  • Всё ли сделано по инструкции с сайта debian.org
  • Обновлено ли у вас ядро хотя бы до той версии, что у меня.

Если все так — попробуйте сделать то, что советует virtualbox

/etc/init.d/vboxdrv setup

Однако, этого пути может и не существовать.

Есть форумы, где обсуждалась эта проблема — поyahooярьте, пояндексите. Правда, когда
у меня на ноутбуке возникла такая проблема, ничего
оттуда не помогло. Но у меня было старое ядро!

your current centos software installation requires of available space

При попытке установить новую вирутальную ОС может появиться
следующая ошибка

virtualbox your current centos software installation requires of available space including for software and for swap space

Нажмите Reclaim Space

Создание host-only адаптера в VirtualBox изображение с сайта www.andreyolegovich.ru

reclaim space


ww.andreyolegovich.ru

Создание host-only адаптера в VirtualBox изображение с сайта www.andreyolegovich.ru
reclaim space


ww.andreyolegovich.ru

Kernel driver not installed (rc=-1908)

Довольно затруднительная ситуация когда при выполнении

virtualbox

Получаете предупреждение

WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.

А в UI следующая ошибка

Kernel driver not installed (rc 1908) в VirtualBox изображение с сайта www.andreyolegovich.ru

rc=-1908


ww.andreyolegovich.ru

Попытки установить всё перечисленное выше и сделать apt upgrade могут не принести результата

sudo apt install virtualbox-dkms

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
libfprint-2-tod1 libllvm10 libllvm10:i386 linux-headers-5.4.0-59
linux-headers-5.4.0-59-generic linux-headers-5.6.0-1020-oem
linux-headers-5.6.0-1036-oem linux-headers-5.6.0-1039-oem
linux-image-5.4.0-59-generic linux-image-5.6.0-1020-oem
linux-image-5.6.0-1036-oem linux-image-5.6.0-1039-oem
linux-modules-5.4.0-59-generic linux-modules-5.6.0-1020-oem
linux-modules-5.6.0-1036-oem linux-modules-5.6.0-1039-oem
linux-modules-extra-5.4.0-59-generic
linux-modules-nvidia-450-5.4.0-59-generic linux-oem-5.6-headers-5.6.0-1020
linux-oem-5.6-headers-5.6.0-1036 linux-oem-5.6-headers-5.6.0-1039
Use ‘sudo apt autoremove’ to remove them.
The following additional packages will be installed:
linux-headers-5.4.0-60 linux-headers-5.4.0-60-generic
The following NEW packages will be installed:
linux-headers-5.4.0-60 linux-headers-5.4.0-60-generic linux-headers-generic
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 12.2 MB of archives.
After this operation, 85.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-60 all 5.4.0-60.67 [11.0 MB]
Get:2 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-60-generic amd64 5.4.0-60.67 [1,232 kB]
Get:3 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-generic amd64 5.4.0.60.63 [2,468 B]
Fetched 12.2 MB in 2s (6,333 kB/s)
Selecting previously unselected package linux-headers-5.4.0-60.
(Reading database … 382700 files and directories currently installed.)
Preparing to unpack …/linux-headers-5.4.0-60_5.4.0-60.67_all.deb …
Progress: [ 8%] [#####………………………………………………………..]
Selecting previously unselected package linux-headers-5.4.0-60-generic……………………..]
Preparing to unpack …/linux-headers-5.4.0-60-generic_5.4.0-60.67_amd64.deb …
Unpacking linux-headers-5.4.0-60-generic (5.4.0-60.67) …
Selecting previously unselected package linux-headers-generic.
Preparing to unpack …/linux-headers-generic_5.4.0.60.63_amd64.deb …
Unpacking linux-headers-generic (5.4.0.60.63) …
Setting up linux-headers-5.4.0-60 (5.4.0-60.67) …
Setting up linux-headers-5.4.0-60-generic (5.4.0-60.67) …
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-60-generic

Kernel preparation unnecessary for this kernel. Skipping…
applying patch disable_fstack-clash-protection_fcf-protection.patch…patching file Kbuild
Hunk #1 succeeded at 84 (offset 13 lines).

Building module:
cleaning build area…
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 ‘make’ -j8 NV_EXCLUDE_BUI
LD_MODULES=» KERNEL_UNAME=5.4.0-60-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/mod
Progress: [ 69%] [#######################################………..#####…………………….]
Signing module:
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia-uvm.ko
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia.ko
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia-modeset.ko
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia-drm.ko
Nothing to do.
cleaning build area…

DKMS: build completed.

nvidia.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

nvidia-modeset.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

nvidia-drm.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

nvidia-uvm.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

depmod…

DKMS: install completed.

Kernel preparation unnecessary for this kernel. Skipping…

Building module:
cleaning build area…
make -j8 KERNELRELEASE=5.4.0-60-generic -C /lib/modules/5.4.0-60-generic/build M=/var/lib/dkms/virtual
box/6.1.10/build……
Signing module:
— /var/lib/dkms/virtualbox/6.1.10/5.4.0-60-generic/x86_64/module/vboxdrv.ko
— /var/lib/dkms/virtualbox/6.1.10/5.4.0-60-generic/x86_64/module/vboxnetadp.ko
— /var/lib/dkms/virtualbox/6.1.10/5.4.0-60-generic/x86_64/module/vboxnetflt.ko
Nothing to do.
cleaning build area…

DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

vboxnetadp.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

vboxnetflt.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

depmod…

DKMS: install completed.
…done.
Setting up linux-headers-generic (5.4.0.60.63) …

sudo modprobe vboxdrv

modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.8.0-34-generic

sudo dpkg-reconfigure virtualbox-dkms

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.4.0-60-generic (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.4.0-60-generic/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.4.0-60-generic/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.4.0-60-generic/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.6.0-1036-oem (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1036-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1036-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1036-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.6.0-1039-oem (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1039-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1039-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1039-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.6.0-1042-oem (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1042-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1042-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1042-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——————————
Deleting module version: 6.1.10
completely from the DKMS tree.
——————————
Done.
Loading new virtualbox-6.1.10 DKMS files…
Building for 5.8.0-34-generic 5.8.0-36-generic
Building initial module for 5.8.0-34-generic
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/virtualbox-dkms.0.crash’
Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.

sudo dpkg-reconfigure virtualbox

Job for vboxweb.service failed because the service did not take the steps required by its unit configuration.
See «systemctl status vboxweb.service» and «journalctl -xe» for details.
Job for virtualbox.service failed because the control process exited with error code.
See «systemctl status virtualbox.service» and «journalctl -xe» for details.
invoke-rc.d: initscript virtualbox, action «restart» failed.
virtualbox.service — LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; generated)
Active: failed (Result: exit-code) since Fri 2021-01-08 15:31:23 EET; 4ms ago
Docs: man:systemd-sysv-generator(8)
Process: 66734 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Jan 08 15:31:23 LL-USER2 systemd[1]: Starting LSB: VirtualBox Linux kernel module…
Jan 08 15:31:23 LL-USER2 virtualbox[66734]: * Loading VirtualBox kernel modules…
Jan 08 15:31:23 LL-USER2 virtualbox[66734]: * No suitable module for running kernel found
Jan 08 15:31:23 LL-USER2 virtualbox[66734]: …fail!
Jan 08 15:31:23 LL-USER2 systemd[1]: virtualbox.service: Control process exited, code=exited, status=1/FAILURE
Jan 08 15:31:23 LL-USER2 systemd[1]: virtualbox.service: Failed with result ‘exit-code’.
Jan 08 15:31:23 LL-USER2 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.

Содержание man SYSTEMD-SYSV-GENERATOR (8)

SYSTEMD-SYSV-GENERATOR (8)
systemd-sysv-generator S
NAME
systemd-sysv-generator — Unit generator for SysV init scripts
SYNOPSIS
/lib/systemd/system-generators/systemd-sysv-generator
DESCRIPTION
systemd-sysv-generator is a generator that creates wrapper .service
units for SysV init[1] scripts in /etc/init.d/* at boot and when
configuration of the system manager is reloaded. This will allow
systemd(1) to support them similarly to native units.
LSB headers[2] in SysV init scripts are interpreted, and the ordering
specified in the header is turned into dependencies between the
generated unit and other units. The LSB facilities «$remote_fs»,
«$network», «$named», «$portmap», «$time» are supported and will be
turned into dependencies on specific native systemd targets. See
systemd.special(7) for more details.
SysV runlevels have corresponding systemd targets (runlevelX.target).
The wrapper unit that is generated will be wanted by those targets
which correspond to runlevels for which the script is enabled.
systemd does not support SysV scripts as part of early boot, so all
wrapper units are ordered after basic.target.
systemd-sysv-generator implements systemd.generator(7).
SEE ALSO
systemd(1), systemd.service(5), systemd.target(5)
NOTES
1.
SysV init
https://savannah.nongnu.org/projects/sysvinit
2.
LSB headers
http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
systemd 245 SYSTEMD-SYSV-GENERATOR(8)

sudo apt install —reinstall linux-headers-$(uname -r) virtualbox-dkms dkms

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
libfprint-2-tod1 libllvm10 libllvm10:i386 linux-headers-5.4.0-59 linux-headers-5.4.0-59-generic
linux-headers-5.6.0-1020-oem linux-headers-5.6.0-1036-oem linux-headers-5.6.0-1039-oem
linux-image-5.4.0-59-generic linux-image-5.6.0-1020-oem linux-image-5.6.0-1036-oem
linux-image-5.6.0-1039-oem linux-modules-5.4.0-59-generic linux-modules-5.6.0-1020-oem
linux-modules-5.6.0-1036-oem linux-modules-5.6.0-1039-oem linux-modules-extra-5.4.0-59-generic
linux-modules-nvidia-450-5.4.0-59-generic linux-oem-5.6-headers-5.6.0-1020
linux-oem-5.6-headers-5.6.0-1036 linux-oem-5.6-headers-5.6.0-1039
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 1 not upgraded.
Need to get 1,990 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 dkms all 2.8.1-5ubuntu1 [66.6 kB]
Get:2 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.8.0-34-generic amd64 5.8.0-34.37~20.04.2 [1,236 kB]
Get:3 http://fi.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 virtualbox-dkms amd64 6.1.10-dfsg-1~ubuntu1.20.04.1 [687 kB]
Fetched 1,990 kB in 0s (7,308 kB/s)
(Reading database … 412468 files and directories currently installed.)
Preparing to unpack …/dkms_2.8.1-5ubuntu1_all.deb …
Unpacking dkms (2.8.1-5ubuntu1) over (2.8.1-5ubuntu1) …
Preparing to unpack …/linux-headers-5.8.0-34-generic_5.8.0-34.37~20.04.2_amd64.deb …
Unpacking linux-headers-5.8.0-34-generic (5.8.0-34.37~20.04.2) over (5.8.0-34.37~20.04.2) …
Preparing to unpack …/virtualbox-dkms_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb …

——————————
Deleting module version: 6.1.10
completely from the DKMS tree.
——————————
Done.
Unpacking virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) over (6.1.10-dfsg-1~ubuntu1.20.04.1) …
Setting up linux-headers-5.8.0-34-generic (5.8.0-34.37~20.04.2) …
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.8.0-34-generic
…done.
Setting up dkms (2.8.1-5ubuntu1) …
Setting up virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) …
Loading new virtualbox-6.1.10 DKMS files…
Building for 5.8.0-34-generic 5.8.0-36-generic
Building initial module for 5.8.0-34-generic
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/virtualbox-dkms.0.crash’
Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
dpkg: error processing package virtualbox-dkms (—configure):
installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
Processing triggers for man-db (2.9.1-1) …
Errors were encountered while processing:
virtualbox-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

This system is currently not set up to build kernel modules.

This system is currently not set up to build kernel modules.
Please install the gcc make perl packages from your distribution.
modprobe vboxguest failed
The log file /var/log/vboxadd-setup.log may contain further information.

Установите

gcc

В

Rocky
,

CentOS

и RedHat это делается следующим образом

yum install gcc

The VirtualBox kernel modules do not match this version of VirtualBox

RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

‘/sbin/vboxconfig’

may correct this. Make sure that you are not mixing builds of VirtualBox from different sources.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) — The installed support driver doesn’t match the version of the user.

Возможно, существует более цивилизованный способ решения этой проблемы, но мне приходится удалять текущий VirtualBox

sudo apt remove —purge virtualbox
sudo apt install virtualbox

Иногда рекомендуют установить также virtualbox-dkms

sudo apt install virtualbox-dkms

Однажды мне помогло скачивание новой версии и устанавка из .deb

sudo dpkg -i virtualbox-6.1_6.1.28-147628~Ubuntu~eoan_amd64.deb

Nonexistent host networking interface

VBoxManage: error: Nonexistent host networking interface, name » (VERR_INTERNAL_ERROR)

Выполните, заменив ubuntu20 на имя вашей машины

VBoxManage showvminfo ubuntu20

У какого-то интерфейса вы обнаружите пустое место там где должно быть название сети. В данном примере
это NIC 1

NIC 1: MAC: 08002706DACE, Attachment: Host-only Interface » Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none

Убедитесь, что у вас есть нужная сеть и добавьте интерфейс туда

VBoxManage modifyvm ubuntu20 —nic1 hostonly —hostonlyadapter1 vboxnet0

Подробнее читайте в статье

«Подключение сетевого адаптераф»

Cannot unregister the machine

VBoxManage: error: Cannot unregister the machine ‘ubuntu’ while it is locked

Значит, что ваша машина в данный момент запущена.

Скорее всего в режиме headless, иначе бы вы её увидели и выключили бы.

Нужно найти запущенный процесс и закончить его. Например, с помощью

grep

ps -A | grep VBoxHeadless

10226 ? 00:01:01 VBoxHeadless

kill -9 10226

Или с помощью

awk

kill $(ps -A | grep VBoxHeadless | awk {‘print $1’})

Похожие статьи

VirtualBox
Установка
Виртуальная CentOS 7 на Ubuntu
Терминал VirtualBox
Windows 7 на VirtualBox Debian
NatNetwork
VBoxManage Manual
Разбор ошибок
DevOps
CentOS
Ubuntu

Понравилась статья? Поделить с друзьями:
  • Error module rewrite does not exist
  • Error module php8 does not exist
  • Error module php7 does not exist
  • Error module php5 does not exist
  • Error module not specified intellij idea