Virtualbox kernel error

I tried to set up an virtual machine on Ubuntu 12.10.I installed Oracle Vm VirtualBox Manager. Then, i followed the steps and i choose .iso file from settings>storage.Then clicked live cd/dvd optio...

I tried to set up an virtual machine on Ubuntu 12.10.I installed Oracle Vm VirtualBox Manager.
Then, i followed the steps and i choose .iso file from settings>storage.Then clicked live cd/dvd option.Then OK,when i clicked to start button i get such an error :

 Kernel driver not installed (rc=-1908)

 The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a                   
 permissionproblem 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 reinstalled program and rebooted pc, but not worked.Also, updated kernel driver but not worked.What can be done to solve it ?

Óscar Andreu's user avatar

asked Dec 2, 2012 at 14:25

2

Thought I’d give my 2 cents for those who use MACs

sudo /Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

answered Nov 12, 2013 at 22:31

Alex's user avatar

AlexAlex

8138 silver badges15 bronze badges

11

sudo apt-get remove virtualbox-dkms
sudo apt-get install virtualbox-dkms

source: http://ubuntuforums.org/showthread.php?t=1885936&page=6

ps. I have this issue everytime I get a Linux kernel update in Ubuntu. The instructions that it gives do not work for me but these two commands work everytime. It would be nice if everytime I got a kernel update these two commands would automatically run afterwards…

answered Mar 25, 2013 at 13:09

Elijah Lynn's user avatar

Elijah LynnElijah Lynn

11.8k10 gold badges58 silver badges86 bronze badges

2

I have a solution that works for MacOS users:

  1. You have to restart your system and press Command (⌘) + R during the loading. It will start the Recovery mode.

  2. Now that you’re on the Recovery Mode, click on Utilities (top bar) and Terminal.

  3. You have your terminal opened? Enter, it will add Oracle in the authorisation list to access the kernel.

    spctl kext-consent add VB5E2TV963

  4. Restart again.

You’re welcome.

answered Jun 25, 2019 at 16:07

idkn's user avatar

idknidkn

4122 gold badges7 silver badges13 bronze badges

3

(I’m on a Mac with this solution) I tried the first few answers on this board (so you might need those as well first), but then finally I Allowed Oracle to «load software» under System Preferences -> Security & Privacy -> in the bottom right, click «Allow…»
Then a dialog box with checkbox options might come up, search for Oracle and check the box next to it. Click OK out of everything. (I also updated the preference above the «Allow…» button to Allow apps downloaded from: to «App store and identified developers«)
After all of this I rebooted and I no longer see this -1908 error when running a VM.
Again, I’m on a Mac, running Big Sur 11.2.1.

Dharman's user avatar

Dharman

29.3k21 gold badges80 silver badges131 bronze badges

answered Feb 18, 2021 at 12:04

skittlebiz's user avatar

skittlebizskittlebiz

3503 silver badges8 bronze badges

2

Personally, on my Mac installing the latest version of VirtualBox solved the problem

answered Aug 19, 2018 at 19:49

Vic Seedoubleyew's user avatar

Vic SeedoubleyewVic Seedoubleyew

10.4k6 gold badges53 silver badges73 bronze badges

1

Goto BIOS setup and Make secure boot Disable
It worked for me.

answered Mar 31, 2019 at 11:42

Sachin Patil's user avatar

Had recently the same problem on Ubuntu 18.04. Apparently, virtual box 6.+ has some issues with gcc-7. These steps did the job for me:

Removing virtualbox

sudo apt-get purge virtualbox-*

installing gcc-8

sudo apt-get install gcc-8 g++-8

setting default gcc to gcc-8

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 800 --slave /usr/bin/g++ g++ /usr/bin/g++-8

and reinstalling virtualbox with the debian installer did it for me!

answered Feb 20, 2020 at 20:05

Thommy257's user avatar

Thommy257Thommy257

7036 silver badges21 bronze badges

0

did you try the command /etc/init.d/vboxdrv setup
What was the output ?

answered Dec 2, 2012 at 14:36

Kasper Jan Mooijman's user avatar

5

First you have to install dkms packages (but optional)

sudo apt-get install dkms

Then run this

sudo /etc/init.d/vboxdrv setup

But in my case I had to run only second one.

answered Sep 15, 2015 at 5:15

Kishan Pradhan's user avatar

Follow the following steps for Linux:

  1. cd /etc/yum.repos.d/
  2. vim epel.repo
  3. Make every "enabled=1"
  4. yum install dkms

Ivan Aracki's user avatar

Ivan Aracki

4,56311 gold badges58 silver badges69 bronze badges

answered Jan 24, 2016 at 9:52

Pravin Ranjan's user avatar

there were only linux-lts kernel in my system so far. i just install linux-lts-headers using pacman and then i rebooted pc.it worked for me.

answered Jul 7, 2019 at 3:24

sashi singh's user avatar

1

This one in recovery mode answered by @idkn worked for me.

spctl kext-consent add VB5E2TV963

answered Dec 8, 2019 at 11:13

vipin goyal's user avatar

vipin goyalvipin goyal

65111 silver badges16 bronze badges

The below code seems to fix the error. It might recur when you update your distrbution, so make sure to rerun it.

sudo modprobe vboxdrv

answered Dec 22, 2019 at 18:22

Muhammad Asif Mohtesham's user avatar

0

did you try the command:

sudo kextload /Library/Extensions/VBoxDrv.kext/

answered Apr 17, 2014 at 17:36

Gere's user avatar

GereGere

2,03424 silver badges23 bronze badges

2

Firstly open a terminal and write this command:

  • sudo apt-get remove virtualbox-dkms

and after finish this operation, write this command:

  • sudo apt-get install virtualbox-dkms

This solved the problem.
Do not worry, your files will not be lost.

Ivan Aracki's user avatar

Ivan Aracki

4,56311 gold badges58 silver badges69 bronze badges

answered Sep 13, 2018 at 9:12

Ali Haydar Toprak's user avatar

I had the same problem and I fixed it by running this command:
sudo /etc/init.d/vboxdrv setup

Ivan Aracki's user avatar

Ivan Aracki

4,56311 gold badges58 silver badges69 bronze badges

answered Mar 24, 2015 at 16:20

Fariba's user avatar

FaribaFariba

6531 gold badge11 silver badges27 bronze badges

I tried to set up an virtual machine on Ubuntu 12.10.I installed Oracle Vm VirtualBox Manager.
Then, i followed the steps and i choose .iso file from settings>storage.Then clicked live cd/dvd option.Then OK,when i clicked to start button i get such an error :

 Kernel driver not installed (rc=-1908)

 The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a                   
 permissionproblem 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 reinstalled program and rebooted pc, but not worked.Also, updated kernel driver but not worked.What can be done to solve it ?

Óscar Andreu's user avatar

asked Dec 2, 2012 at 14:25

2

Thought I’d give my 2 cents for those who use MACs

sudo /Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

answered Nov 12, 2013 at 22:31

Alex's user avatar

AlexAlex

8138 silver badges15 bronze badges

11

sudo apt-get remove virtualbox-dkms
sudo apt-get install virtualbox-dkms

source: http://ubuntuforums.org/showthread.php?t=1885936&page=6

ps. I have this issue everytime I get a Linux kernel update in Ubuntu. The instructions that it gives do not work for me but these two commands work everytime. It would be nice if everytime I got a kernel update these two commands would automatically run afterwards…

answered Mar 25, 2013 at 13:09

Elijah Lynn's user avatar

Elijah LynnElijah Lynn

11.8k10 gold badges58 silver badges86 bronze badges

2

I have a solution that works for MacOS users:

  1. You have to restart your system and press Command (⌘) + R during the loading. It will start the Recovery mode.

  2. Now that you’re on the Recovery Mode, click on Utilities (top bar) and Terminal.

  3. You have your terminal opened? Enter, it will add Oracle in the authorisation list to access the kernel.

    spctl kext-consent add VB5E2TV963

  4. Restart again.

You’re welcome.

answered Jun 25, 2019 at 16:07

idkn's user avatar

idknidkn

4122 gold badges7 silver badges13 bronze badges

3

(I’m on a Mac with this solution) I tried the first few answers on this board (so you might need those as well first), but then finally I Allowed Oracle to «load software» under System Preferences -> Security & Privacy -> in the bottom right, click «Allow…»
Then a dialog box with checkbox options might come up, search for Oracle and check the box next to it. Click OK out of everything. (I also updated the preference above the «Allow…» button to Allow apps downloaded from: to «App store and identified developers«)
After all of this I rebooted and I no longer see this -1908 error when running a VM.
Again, I’m on a Mac, running Big Sur 11.2.1.

Dharman's user avatar

Dharman

29.3k21 gold badges80 silver badges131 bronze badges

answered Feb 18, 2021 at 12:04

skittlebiz's user avatar

skittlebizskittlebiz

3503 silver badges8 bronze badges

2

Personally, on my Mac installing the latest version of VirtualBox solved the problem

answered Aug 19, 2018 at 19:49

Vic Seedoubleyew's user avatar

Vic SeedoubleyewVic Seedoubleyew

10.4k6 gold badges53 silver badges73 bronze badges

1

Goto BIOS setup and Make secure boot Disable
It worked for me.

answered Mar 31, 2019 at 11:42

Sachin Patil's user avatar

Had recently the same problem on Ubuntu 18.04. Apparently, virtual box 6.+ has some issues with gcc-7. These steps did the job for me:

Removing virtualbox

sudo apt-get purge virtualbox-*

installing gcc-8

sudo apt-get install gcc-8 g++-8

setting default gcc to gcc-8

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 800 --slave /usr/bin/g++ g++ /usr/bin/g++-8

and reinstalling virtualbox with the debian installer did it for me!

answered Feb 20, 2020 at 20:05

Thommy257's user avatar

Thommy257Thommy257

7036 silver badges21 bronze badges

0

did you try the command /etc/init.d/vboxdrv setup
What was the output ?

answered Dec 2, 2012 at 14:36

Kasper Jan Mooijman's user avatar

5

First you have to install dkms packages (but optional)

sudo apt-get install dkms

Then run this

sudo /etc/init.d/vboxdrv setup

But in my case I had to run only second one.

answered Sep 15, 2015 at 5:15

Kishan Pradhan's user avatar

Follow the following steps for Linux:

  1. cd /etc/yum.repos.d/
  2. vim epel.repo
  3. Make every "enabled=1"
  4. yum install dkms

Ivan Aracki's user avatar

Ivan Aracki

4,56311 gold badges58 silver badges69 bronze badges

answered Jan 24, 2016 at 9:52

Pravin Ranjan's user avatar

there were only linux-lts kernel in my system so far. i just install linux-lts-headers using pacman and then i rebooted pc.it worked for me.

answered Jul 7, 2019 at 3:24

sashi singh's user avatar

1

This one in recovery mode answered by @idkn worked for me.

spctl kext-consent add VB5E2TV963

answered Dec 8, 2019 at 11:13

vipin goyal's user avatar

vipin goyalvipin goyal

65111 silver badges16 bronze badges

The below code seems to fix the error. It might recur when you update your distrbution, so make sure to rerun it.

sudo modprobe vboxdrv

answered Dec 22, 2019 at 18:22

Muhammad Asif Mohtesham's user avatar

0

did you try the command:

sudo kextload /Library/Extensions/VBoxDrv.kext/

answered Apr 17, 2014 at 17:36

Gere's user avatar

GereGere

2,03424 silver badges23 bronze badges

2

Firstly open a terminal and write this command:

  • sudo apt-get remove virtualbox-dkms

and after finish this operation, write this command:

  • sudo apt-get install virtualbox-dkms

This solved the problem.
Do not worry, your files will not be lost.

Ivan Aracki's user avatar

Ivan Aracki

4,56311 gold badges58 silver badges69 bronze badges

answered Sep 13, 2018 at 9:12

Ali Haydar Toprak's user avatar

I had the same problem and I fixed it by running this command:
sudo /etc/init.d/vboxdrv setup

Ivan Aracki's user avatar

Ivan Aracki

4,56311 gold badges58 silver badges69 bronze badges

answered Mar 24, 2015 at 16:20

Fariba's user avatar

FaribaFariba

6531 gold badge11 silver badges27 bronze badges

Today I noticed that my VirtualBox VMs no longer start. With messages

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

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine
Unknown macro: {b2547866-a0a1-4391-8b86-6952d82efaa0} 

And

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/sbin/vboxconfig'

as root.

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

It seems this is caused by a kernel update. I actually wasn’t aware that Ubuntu is doing automatic kernel updates. The log /var/log/dpkg.log shows that kernel update was going on right before problems started.

sudo dpkg --list | grep linux-image shows images lines with many 4.8, 4.10 and 4.13 versions.

[user:~] $ uname -a
Linux io 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

The suggested solution for this problem unfortunately does not work.

[root:~] # /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
depmod: ERROR: could not open directory /lib/modules/4.10.0-27-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-28-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-30-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-32-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-33-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-35-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-37-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-38-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.10.0-40-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-41-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-45-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-46-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-49-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-52-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-54-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-56-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.8.0-58-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
[root:~] # 

The install log /var/log/vbox-install.log is too large to post here but it starts with following message

make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (        
echo >&2;                           
echo >&2 "  ERROR: Kernel configuration is invalid.";       
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";  
echo >&2 ;  

There are actually three questions now I think
* How do I fix kernel configuration?
* How do I fix VirtualBox? Should I remove and reinstall?
* How do I prevent these types of issues? Should I disable auto-updates of kernel?

enter image description here
enter image description here

  • Печать

Страницы: [1]   Вниз

Тема: Ошибка Kernel driver not installed (rc=-1908) Virtualbox  (Прочитано 15934 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
ubuntu beginner

При попытке запуска виртуальной машины появляется ошибка 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.


Пробовала ‘modprobe vboxdrv’, как советовала ошибка, директории не существует,в чём я после этого благополучно убедилась. Удалила ‘virtualbox-dkms’, при попытке установить его снова

● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; generated)
   Active: failed (Result: exit-code) since Thu 2018-10-04 23:44:55 EET; 19ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 21085 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

окт 04 23:44:55 myPC systemd[1]: Starting LSB: VirtualBox Linux kernel module...
окт 04 23:44:55 myPC virtualbox[21085]:  * Loading VirtualBox kernel modules...
окт 04 23:44:55 myPC virtualbox[21085]:  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
окт 04 23:44:55 myPC virtualbox[21085]:    ...fail!
окт 04 23:44:55 myPC systemd[1]: virtualbox.service: Control process exited, code=exited status=1
окт 04 23:44:55 myPC systemd[1]: virtualbox.service: Failed with result 'exit-code'.
окт 04 23:44:55 myPC systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.


И конечно же, при запуске 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.


Заголовки для ядра установлены.
Люди добрые, помогите, пожалуйста, решить проблему! Излазила кучу сайтов, форумов, ничего не помогает :(

« Последнее редактирование: 05 Октября 2018, 01:08:56 от ubuntu beginner »


Dzhoser

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.

Поддержка виртуального драйвера Linux не загружена или проблемы с доступом к /dev/vboxdrv. Подалуста переустановите virtualbox-dkms пакет и загрузите модуль ядра с параметром modprobe virtualbox как root


Пользователь добавил сообщение 05 Октября 2018, 10:38:07:


Как ставите?


Оффлайн
ecc83

ubuntu beginner, у меня достаточно давно установлен virtualbox. Устанавливал отсюда.
Добавил их репозиторий и установил последнюю версию. Всё работает отлично.
Перед установкой данного пакета, необходимо удалить все предыдущие эксперименты.


Оффлайн
xuser73

sudo /sbin/vboxconfig на 16.04 мне помогла, когда появились проблемы с драйвером виртуалбокса. Это было, кажется, после обновления ядра.

Настоящему коту всегда март.


Оффлайн
ubuntu beginner

Dzhoser, пробовала переустанавливать virtualbox-dkms несколько раз, никак не встаёт из-за неведомой ошибки. Не подскажете, как выявить пролемы с доступом? и с чем они могут быть связаны?


Пользователь добавил сообщение 09 Октября 2018, 00:51:46:


xuser73, команда не найдена :(

« Последнее редактирование: 09 Октября 2018, 00:51:46 от ubuntu beginner »


Оффлайн
ALiEN175

ubuntu beginner, уверены, что заголовки ядра стоят? По всем симптомам — похоже, не установлены.

Покажите на всякий:

sudo dpkg -l | grep headers
И еще, самое важное — есть ли поддержка виртуализации в самом процессоре

grep -E '(vmx|svm)' /proc/cpuinfo

« Последнее редактирование: 09 Октября 2018, 04:35:01 от ALiEN175 »

ASUS P5K-C :: Intel Xeon E5450 @ 3.00GHz :: 8 GB DDR2 :: Radeon R7 260X :: XFCE
ACER 5750G :: Intel Core i5-2450M @ 2.50GHz :: 6 GB DDR3 :: GeForce GT 630M :: XFCE


Dzhoser

Dzhoser, пробовала переустанавливать virtualbox-dkms несколько раз, никак не встаёт из-за неведомой ошибки. Не подскажете, как выявить пролемы с доступом? и с чем они могут быть связаны?

Запустите в терминале,ошибку сюда скопируйте.


Оффлайн
ubuntu beginner

ALiEN175,
Вывод команды «sudo dpkg -l | grep headers»

ii  linux-generic                              4.15.0.34.36                        amd64        Complete Generic Linux kernel and headers
ii  linux-headers-4.15.0-29                    4.15.0-29.31                        all          Header files related to Linux kernel version 4.15.0
ii  linux-headers-4.15.0-29-generic            4.15.0-29.31                        amd64        Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii  linux-headers-4.15.0-34                    4.15.0-34.37                        all          Header files related to Linux kernel version 4.15.0
ii  linux-headers-4.15.0-34-generic            4.15.0-34.37                        amd64        Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii  linux-headers-generic                      4.15.0.34.36                        amd64        Generic Linux kernel headers
ii  linux-signed-generic                       4.15.0.34.36                        amd64        Complete Signed Generic Linux kernel and headers (dummy transitional package)
А это «grep -E ‘(vmx|svm)’ /proc/cpuinfo»

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat


Пользователь добавил сообщение 09 Октября 2018, 23:09:42:


Dzhoser, это я снова пытаюсь установить virtualbox-dkms из aptitude

Следующие НОВЫЕ пакеты будут установлены:       
  virtualbox-dkms
0 пакетов обновлено, 1 установлено новых, 0 пакетов отмечено для удаления, и 86 пакетов не обновлено.
Необходимо получить 0 Б/657 kБ архивов. После распаковки 5 408 kБ будет занято.
Выбор ранее не выбранного пакета virtualbox-dkms.
(Чтение базы данных … на данный момент установлено 175040 файлов и каталогов.)
Подготовка к распаковке …/virtualbox-dkms_5.2.10-dfsg-6ubuntu18.04.1_all.deb …
Распаковывается virtualbox-dkms (5.2.10-dfsg-6ubuntu18.04.1) …
Настраивается пакет virtualbox-dkms (5.2.10-dfsg-6ubuntu18.04.1) …
Loading new virtualbox-5.2.10 DKMS files...
Building for 4.15.0-34-generic
Building initial module for 4.15.0-34-generic
Done.

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

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

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

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/

depmod...

DKMS: install completed.
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 Tue 2018-10-09 22:08:00 EET; 30ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 10475 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

окт 09 22:08:00 myPC systemd[1]: Starting LSB: VirtualBox Linux kernel module...
окт 09 22:08:00 myPC virtualbox[10475]:  * Loading VirtualBox kernel modules...
окт 09 22:08:00 myPC virtualbox[10475]:  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
окт 09 22:08:00 myPC virtualbox[10475]:    ...fail!
окт 09 22:08:00 myPC systemd[1]: virtualbox.service: Control process exited, code=exited status=1
окт 09 22:08:00 myPC systemd[1]: virtualbox.service: Failed with result 'exit-code'.
окт 09 22:08:00 myPC systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.

« Последнее редактирование: 09 Октября 2018, 23:09:42 от ubuntu beginner »


Оффлайн
ARTGALGANO

ubuntu beginner, secure boot отключен?


Оффлайн
ubuntu beginner

ARTGALGANO, как раз таки включен. в процессе установки virtualbox-dkms терминал просил поставить пароль на secure boot


Оффлайн
ARTGALGANO


Оффлайн
ubuntu beginner

ARTGALGANO, как это сделать?


Пользователь добавил сообщение 10 Октября 2018, 01:07:15:


ARTGALGANO, OMG! Получилось! :D Я отключила secure boot через BIOS, встал пакет virtualbox-dkms, сделала modprobe vboxdrv, и вуяля! Моя виртуальная машина запустилась))) Спасибо большое!)

« Последнее редактирование: 10 Октября 2018, 01:07:15 от ubuntu beginner »


  • Печать

Страницы: [1]   Вверх

Понравилась статья? Поделить с друзьями:
  • Virtualbox extension pack error
  • Virtualbox error relaunching virtualbox process 5
  • Virtualbox error ntcreatefile
  • Virt install error unrecognized arguments
  • Vga post error