O VirtualBox estava trabalhando no meu computador até alguns dias atrás, quando modifiquei o GRUB ao tentar personalizar o Tema. Algo que fiz começou a fazer com que o GRUB fosse carregado em uma tela roxa escura em branco. A menos que eu escolha Opções avançadas no menu GRUB e selecione 4.10.0-37-generic
Kernel. Nesse caso, carregaria normalmente.
Opcionalmente, eu tenho 4.10.0-16-genérico como uma opção também. Mas selecionando as botas para uma tela em branco.
Achei que estava tudo bem, mas descobri que não podia mais executar vagrant up
, que inicia automaticamente uma instância do VirtualBox que tenho em minha máquina. Ele reclamou com o erro abaixo:
The provider 'virtualbox' that was requested to back the machine default is reporting that it isn't usable on this system. The reason is shown below:
VirtualBox is complaining that the kernel module is not loaded. Please run VBoxManage --version or open the VirtualBox GUI to see the error message which should contain instructions on how to fix this error.
Ao executar VBoxManage --version
no Terminal, obtenho:
WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (4.10.0-37-generic) or it failed to load. Please recompile the kernel module and install it by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed. 5.1.30r1183891
Ao executar sudo /sbin/vboxconfig
, obtenho:
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.10.0-37-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root.
Então, eu executo sudo apt-get install linux-headers-4.10.0-37-generic
e recebo:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-4.10.0-37-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
E: Package 'linux-headers-4.10.0-37-generic' has no installation candidate
Então eu pesquisei no Google por esse pacote e basicamente nada volta. Então, relendo o erro acima, pensei que deveria atualizar. Então eu executei 'e recebo este erro, que acredita ser a raiz do erro anterior:
Hit:12 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu artful InRelease
Ign:13 http://download.virtualbox.org/virtualbox/debian artful InRelease
Hit:14 http://download.virtualbox.org/virtualbox/debian zesty InRelease
Err:15 http://download.virtualbox.org/virtualbox/debian artful Release
404 Not Found [IP: 23.215.104.186 80]
Reading package lists... Done
E: The repository 'http://download.virtualbox.org/virtualbox/debian artful Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Então eu executei sudo apt-get install virtualbox-ext-pack
e abaixo está a saída, mas o que mais me chamou a atenção foi Module build for kernel 4.10.0-37-generic was skipped since the kernel headers for this kernel does not seem to be installed.
link
Eu tenho dois problemas
- preciso superar esse erro inicial.
- Eu não entendo como o servidor / URL oficial do VirtualBox está falhando assim. É o que é especificado em seus documentos oficiais. Eu não sei para onde ir daqui.