kernel driver not installed rc 1908 virtualbox mac os что делать
Ошибка «Kernel driver not installed (rc=-1908)» в VirtualBox (РЕШЕНО)
При запуске виртуальной машины VirtualBox может возникнуть ошибка:
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
В ней говориться, что необходимо загрузить модули ядра VirtualBox.
На самом деле, всё не так просто и скорее всего запуск /sbin/vboxconfig не поможет (если по этому пути вообще что-то есть).
Дело в том, что при установке VirtualBox необходимые свои модули эта программа добавляет в автозагрузку. Следовательно, если загрузка не произошла, значит на это имеется причина.
Попробуйте заново установить VirtualBox. Во-первых, использование правильных команд может просто решить проблему. Если проблема не разрешится, то изучите все записи, которые появятся во время установки — в них может содержаться ключ к дальнейшим действиям.
Для Debian и производных (Ubuntu, Linux Mint, Kali Linux) вы можете установить VirtualBox из стандартных репозиториев:
Для в Arch Linux и производных (BlackArch и другие) вы можете установить VirtualBox из стандартных репозиториев:
Пример ошибки, в которой содержится подсказка:
В ней говориться, что невозможно установить модуль vboxhost, поскольку отсутствуют заголовки ядра. В этом случае нужно установить пакет с заголовками для вашей версии ядра. Примерное название пакета: linux-headers.
После установки заголовков, заново переустановите DKMS. Ошибка должна исчезнуть.
Если всё прошло хорошо, можно необходимый модуль запустить вручную:
Но рекомендуется просто перезагрузить компьютер, поскольку другие модули VirtualBox также не запущены и будут появляться новые ошибки.
Если это всё не помогло, то продолжаем разбираться.
Теперь для запуска модулей ядра используется служба virtualbox.service, проверьте её статус и, если она не работает, то какая выводится ошибка:
Также посмотрите, какие ошибки имеются связанные с модулями VirtualBox:
Попробуйте запустить модуль вручную:
Возможно в полученных ошибках будет подсказка для дальнейших действий.
== Далее устаревшая информация, она оставлена для тех, у кого старая версия VirtualBox ==
virtualbox-host-modules-arch и virtualbox-host-dkms используют службу systemd-modules-load.service для автоматической загрузки всех четырёх модулей VirtualBox при старте компьютера. Поэтому проверьте статус этой службы:
Если она не запущена, запустите её и добавьте в автозагрузку.
Как исправить ошибку Kernel driver not installed (rc=-1908) в VirtualBox на macOS
Пользователи macOS (в особенности Big Sur) сталкиваются со следующей ошибкой при использовании виртуализации VirtualBox от Oracle:
Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.
where: suplibOsInit what: 3
VERR_VM_DRIVER_NOT_INSTALLED
(-1908) — The support driver is not installed.
On linux, open returned ENOENT.
Исправить эту ошибку крайне просто. Вероятнее всего, причина её возникновения в том, что на этапе установки VirtualBox вы проигнорировали уведомление о том, что в настойках нужно предоставить одно из разрешений:
Чтобы исправить это, перейдите в «Системные настройки» macOS, откройте раздел «Защита и безопасность». В нём снимите замок в левом нижнем углу, а затем кликните на кнопку «Разрешить» рядом с появившемся пунктом «Загрузка системного ПО разработчика „Oracle America, Inc.” была заблокирована».
Если этого пункта у вас нет, попробуйте переустановить VirtualBox.
Kernel driver not installed rc 1908 virtualbox mac os что делать
5 Answers 5
Go to Security and Privacy / General in your System Settings. You will see that software from Oracle has been blocked. Allow it, and the software will work. The ‘allow Oracle’ option only exists for 30mins after the installer error.
See Apple’s technical note on this.
7,118 3 3 gold badges 23 23 silver badges 46 46 bronze badges
FYI, the option to allow Oracle only lasts for 30mins after the installer error message. See this Virtual Box forum thread and this Apple technical note i have the same Problem but there is nothing to allow in my system settings.
Recently I’ve upgraded to MacOS (Catalina) 10.15.1 and I’ve upgraded to VB 6.0.14 and started getting above issue while starting my earlier guestOs i.e. Ubuntu 18.04LTS.
I’ve tried various solution, but nothing worked except this:
So you need to run this command in recovery mode terminal ONLY (Top Menu Bar » Utilities » Terminal). I was avoiding going into recovery mode but when nothing worked and you don’t have any other option; you can save this command and note it down in some mobile app or notepad.
4 Answers 4
Make sure the kernel module has been loaded successfully.
where the error is:
Download and install the latest VirtualBox 6.1.18 or higher. And then follow the below steps to resolve.
Step 2: Go into System Preferences->Security & Privacy
Step 3: Unlock the security center
Step 4: Approve the software by Oracle
1,164 4 4 gold badges 16 16 silver badges 43 43 bronze badges
Big Sur disables the VirtualBox kernel extensions as part of the installation process. You can verify this by running:
If the kernel extensions are installed, you will see something like this:
If you don’t see the extensions loaded, the easier fix is to delete your current VirtualBox app, download and install the lastest version and then go the Security & Privacy System Preferences Pane. You should see a message that some applications require a restart to work correctly.
Restart your Mac and VirtualBox should now work. You can re-run the kexstat command just to be sure the extensions were loaded.
VirtualBox на Mac — Kernel driver not installed (rc=-1908). Проверенное решение
Проверено как минимум пять раз на разных устройствах и разных версиях MacOS (BigSur, Catalina).
Не торопитесь ничего удалять, или переустанавливать, как это иногда рекомендуют. Паниковать так же не стОит, и даже срочно делать резервную копию не обязательно (хотя в целом это хорошая практика делать регулярные резервные копии).
На этот случай у VirtualBox есть скрипт, который вам поможет всё починить.
Итак,
1. открываем терминал, и выполняем следующую команду:
sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart
2. Вводим свой пароль, и в ответ получаем что-то типа такого:
Таких строк может быть несколько, это не важно.
3. Обратите внимание, что среди всего прочего, в ответе присутствуют просьба перезагрузить систему «requires a reboot». Не сопротивляемся, перезагружаемся. Если не просит, то вывод будет такой как в шаге 5.
4. После перезагрузки, еще раз открываем терминал, и выполняем команду из шага 1.
18 Answers 18
Thought I’d give my 2 cents for those who use MACs
@ChristophH. I did the same as Jannik mentioned. I ran the command then went to Security & Privacy, allowed Oracle, then ran the command again. It should work the second time. VirtualBox has to be closed and it will work on MacOS Big Sur
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.
10.3k 10 10 gold badges 51 51 silver badges 73 73 bronze badges In my case (Ubuntu 20.04) I have to do the same, for each kernel update: sudo apt-get remove virtualbox-dkms sudo apt-get install virtualbox-dkms sudo modprobe vboxdrv the restart the VirtualBox application `
I have a solution that works for MacOS users:
You have to restart your system and press Command (⌘) + R during the loading. It will start the Recovery mode.
Now that you’re on the Recovery Mode, click on Utilities (top bar) and Terminal.
You have your terminal opened? Enter, it will add Oracle in the authorisation list to access the kernel.
spctl kext-consent add VB5E2TV963
23.9k 20 20 gold badges 60 60 silver badges 112 112 bronze badges
Goto BIOS setup and Make secure boot Disable It worked for me.
bash : /etc/init.d/vboxdrv setup : No such file or directory actually,yes i did but i dont know how it went to a way it works, there are lots of recommendations on the internet, it isnt true but i applied whatever i saw, then boom, it works, i hope you find the way how actually it works.
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:
sudo apt-get purge virtualbox-*
sudo apt-get install gcc-8 g++-8
setting default gcc to gcc-8
Kernel driver not installed (rc=-1908) Getting Errors in macOS Big Sur 11.0.1
I just want to work with VirtualBox but now I am getting this type of error.
I could not find a proper solution.
2,255 2 2 gold badges 11 11 silver badges 26 26 bronze badges
155 1 1 gold badge 3 3 silver badges 12 12 bronze badges The error message is quite vague. It says On Linux, open returned ENOENT. What about on macOS? It turns out that I have to explicitly allow VirtualBox in the macOS system preference. Go to System Preferences / Security & Privacy. Click “Allow” in the window below. Reboot System. Now VirtualBox no longer complains about kernel driver.
While trying to install Virtual Box on Mac OS the installation fails and show me the failure message. But still I get a copy of Virtual Box installed. When add a KMDV file and try to start it I get an error saying Kernel driver not installed. I am attaching those messages here. Does others also face similar issue, would be nice to get some views on this.
313 1 1 gold badge 3 3 silver badges 14 14 bronze badges
Kernel driver not installed (rc=-1908) Getting Errors in macOS Big Sur 11.0.1
I just want to work with VirtualBox but now I am getting this type of error.
I could not find a proper solution.
6 Answers 6
Make sure the kernel module has been loaded successfully.
where the error is:
Download and install the latest VirtualBox 6.1.18 or higher. And then follow the below steps to resolve.
Step 2: Go into System Preferences->Security & Privacy
Step 3: Unlock the security center
Step 4: Approve the software by Oracle
There should be a prompt in System Preferences to allow the kernel, which will require a reboot.
Reboot and run command cd ˜/Homestead && vagrant up
Big Sur disables the VirtualBox kernel extensions as part of the installation process. You can verify this by running:
If the kernel extensions are installed, you will see something like this:
If you don’t see the extensions loaded, the easier fix is to delete your current VirtualBox app, download and install the lastest version and then go the Security & Privacy System Preferences Pane. You should see a message that some applications require a restart to work correctly.
Restart your Mac and VirtualBox should now work. You can re-run the kexstat command just to be sure the extensions were loaded.
How to Fix “Kernal Driver Not Installed (rc=-1908)” Error on Mac
Fix: VERR_VM_DRIVER_NOT_INSTALLED (-1908)
Oracle VM VirtualBox is one of the most notorious and free virtual machine hypervisors that is available for macOS along with other paid applications like VMware or Parallel. When you install VirtualBox on your macOS and try to use it by installing a virtual machine, it is very likely that you get the “Kernel driver not installed (rc=-1908)” error message. The error message here does not matter on the operating system that you are trying to install on the virtual machine but rather the problem in question appears when you install Oracle products like VirtualBox for the first time on your Mac.
Kernel Driver Not Installed (rc=-1908) Error Message on Mac
As it turns out, the problem is pretty similar to the VirtualBox installation failed error that appears when you are trying to install VirtualBox on your machine. The error message is caused because the Oracle certificate is blocked by your operating system i.e. macOS. In addition to this, the kernel extensions for VirtualBox are disabled by macOS as well during the installation process which is why you are facing the error message in question here. To resolve this, you will have to allow the Oracle certificate by adding it to the authorization list. This has to be done explicitly by giving VirtualBox the required permissions.
You can do this in multiple ways. First, of all, you can allow the certificate through the System and Privacy settings located in the System Preferences menu. In addition to that, you can also use the terminal on your system and execute a few commands that will load the kernel extensions and allow it to be run on the system. With that said, without further ado, let us show you can do this in more detail so just follow through.
Allow Oracle Certificate through System Preferences
As it turns out, the first way you can resolve this problem is through the System Preferences menu on your machine. When macOS blocks software from loading kernel extensions or anything else, you will be shown a message in the System and Privacy settings.
However, this message is only there for 30 minutes and if you have been facing the error message for a while, you will have to uninstall VirtualBox from your system. Once you have uninstalled VirtualBox, move the App to the trash folder and also delete any remaining files. After doing that, you can go ahead and download the installer again to install VirtualBox on your system. Once you have installed VirtualBox, you will have to quickly follow the instructions given down below within the first 30 minutes or it will disappear again and you will have to start over again. With that said, follow the instructions given down below to allow Oracle through the System Preferences menu:
Allow VirtualBox Kernel Extensions through the Terminal
For the more tech-savvy and hardcore users out there, there is also another way you can resolve the issue which requires you to enter a command to the Terminal prompt. This will do the same thing that we were doing above, just through the Terminal window. In addition, if you choose to follow this method, it won’t require you to reinstall VirtualBox as it did in the method mentioned above as we will be using the Terminal here.
However, to do this, we will have to boot into the Recovery Mode in order to do this. Recovery mode lets you restore Mac to a previous date as well as allowing you to reinstall macOS along with many more other things. Follow the instructions given down below to do this:
Disable Secure Boot on your Mac
If the above methods do not work out for you, in some cases, the issue can also be related to the Secure Boot on your BIOS. Secure Boot is basically a security feature of UEFI, also known as Unified Extensible Firmware Interface. When you have Secure Boot enabled and configured, it can help your computer resist malware attacks and infections. As it turns out, since it is a security feature, it can also cause issues with some applications on your device which could be the case here.
Therefore, you will have to disable it on your machine and see if that works out. To do this, follow the instructions given down below:
In case you are not able to disable Secure Boot from Recovery mode, then in such a case, you will have to get into your BIOS settings and change it from there.