Page 1 of 2

virtualbox, can't get to work[Resolved]

Posted: Wed Nov 11, 2020 6:44 pm
by wutsinterweb
I installed the 6.1 version of Virtualbox and it installed successfully. When I try and set up a virtual install of another OS, such as popos, it won't run it when I'm done. I've watched several videos and I don't see anything I'm doing wrong, but I get errors and the vb won't install.

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 6:48 pm
by wutsinterweb
It says virtualbox kernal drivers not installed. I had even tried the VB version in the software manager first and then uninstalled it just in case when it didn't work.

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 7:17 pm
by wutsinterweb
Now Mint won't boot

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 7:26 pm
by wutsinterweb
It broke my kernal somehow

mint wont boot now broke kernel

Posted: Wed Nov 11, 2020 7:28 pm
by wutsinterweb
I installed virtualbox and now i cant reboot on my tower. It appears my kernal is broken.

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 7:44 pm
by wutsinterweb
I did get it to boot now, but it's not finding the bootloader or something. I had changed my BIOS to turn off secure boot and enabled intel virtualization. ASUS Z97 motherboard.

How do I repair my bootloader while booted in?

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 7:54 pm
by wutsinterweb
sorry, I saw this

https://www.fosslinux.com/1521/boot-rep ... issues.htm

and used it and I am booted now, but my other thread where VBs won't work is still an issue.

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 8:02 pm
by wutsinterweb
I started this thread in the wrong place, I'll start a thread where it belongs

Virtualbox, can't get VBs to boot/install

Posted: Wed Nov 11, 2020 8:06 pm
by wutsinterweb
I tried installing virtualbox using the software manager and got the same error as below, and then removed it.

I've installed VB 6.1 from the VB Site succuessfully, but when I try and set up VBs of Windows and Pop OS and then try to boot/install them, I get the same error, the virtaulbox kernel is not set up or installed correctly yadda yadda.

It goes on to say the support driver is not installed

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 8:13 pm
by karlchen
<mod>
wutsinterweb, could you stop starting threads about the same topic in different sub-forums?
3 such started threads have been merged and the resulting thread moved to Virtualization, because this is where you started the last thread.
</mod>

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 8:15 pm
by wutsinterweb
I noted that I made that mistake I'm sorry.

So as it stands, I can now boot on my tower to Mint 20, but I get that error in Virtualbox as stated when attempting to install images of Popos and Windows Or whatever.

I had forgotten that virtualization is where to make the thread, my apologies!

Does anyone have suggestions?

Re: Virtualbox, can't get VBs to boot/install

Posted: Wed Nov 11, 2020 8:22 pm
by RIH
wutsinterweb wrote:
Wed Nov 11, 2020 8:06 pm
I get the same error, the virtaulbox kernel is not set up or installed correctly yadda yadda.

It goes on to say the support driver is not installed
If you expect help then you have to quote EXACTLY what the error message is.
A screen shot would be even better...

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 9:39 pm
by wutsinterweb
screenshot
screenshot
That's it.

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 10:19 pm
by linux-rox
Open Terminal. Run mokutil --sb-state. What's the response?

Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 10:36 pm
by wutsinterweb

Code: Select all

bucky2@bucky2:~$ mokutil --sb-state
This system doesn't support Secure Boot
bucky2@bucky2:~$ 


Re: virtualbox, can't get to work

Posted: Wed Nov 11, 2020 10:37 pm
by wutsinterweb
I had turned off secure boot, it may have been why I had to restore grub?

Re: virtualbox, can't get to work

Posted: Thu Nov 12, 2020 12:54 am
by linux-rox
I asked because it was an issue raised in the error box. Not otherwise familiar with this problem. Good luck.

Re: virtualbox, can't get to work

Posted: Thu Nov 12, 2020 12:58 am
by wutsinterweb
Thank you for trying to help! I will keep hoping a solution can be found and find out why my bootloader failed and had to be restored.

Re: virtualbox, can't get to work

Posted: Thu Nov 12, 2020 1:54 am
by RIH
For the virtualbox issue try this..
https://www.wst.space/virtualbox-kernel ... 08-ubuntu/

(I would suggest that you open a new thread concerning your bootloader issue).

Re: virtualbox, can't get to work

Posted: Thu Nov 12, 2020 4:03 am
by wutsinterweb

Code: Select all

bucky2@bucky2:~$ sudo apt install dkms
[sudo] password for bucky2:                
Reading package lists... Done
Building dependency tree       
Reading state information... Done
dkms is already the newest version (2.8.1-5ubuntu1).
The following packages were automatically installed and are no longer required:
  kbuild linux-headers-5.4.0-40 linux-headers-5.4.0-40-generic
  linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-headers-5.4.0-45
  linux-headers-5.4.0-45-generic linux-headers-5.4.0-47
  linux-headers-5.4.0-47-generic linux-headers-5.4.0-48
  linux-headers-5.4.0-48-generic linux-image-5.4.0-40-generic
  linux-image-5.4.0-42-generic linux-image-5.4.0-45-generic
  linux-image-5.4.0-47-generic linux-image-5.4.0-48-generic
  linux-modules-5.4.0-40-generic linux-modules-5.4.0-42-generic
  linux-modules-5.4.0-45-generic linux-modules-5.4.0-47-generic
  linux-modules-5.4.0-48-generic linux-modules-extra-5.4.0-40-generic
  linux-modules-extra-5.4.0-42-generic linux-modules-extra-5.4.0-45-generic
  linux-modules-extra-5.4.0-47-generic linux-modules-extra-5.4.0-48-generic
  module-assistant virtualbox-source
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
bucky2@bucky2:~$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found
bucky2@bucky2:~$ sudo apt-get remove virtualbox-dkms 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'virtualbox-dkms' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  kbuild linux-headers-5.4.0-40 linux-headers-5.4.0-40-generic
  linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-headers-5.4.0-45
  linux-headers-5.4.0-45-generic linux-headers-5.4.0-47
  linux-headers-5.4.0-47-generic linux-headers-5.4.0-48
  linux-headers-5.4.0-48-generic linux-image-5.4.0-40-generic
  linux-image-5.4.0-42-generic linux-image-5.4.0-45-generic
  linux-image-5.4.0-47-generic linux-image-5.4.0-48-generic
  linux-modules-5.4.0-40-generic linux-modules-5.4.0-42-generic
  linux-modules-5.4.0-45-generic linux-modules-5.4.0-47-generic
  linux-modules-5.4.0-48-generic linux-modules-extra-5.4.0-40-generic
  linux-modules-extra-5.4.0-42-generic linux-modules-extra-5.4.0-45-generic
  linux-modules-extra-5.4.0-47-generic linux-modules-extra-5.4.0-48-generic
  module-assistant virtualbox-source
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
bucky2@bucky2:~$ sudo apt-get 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:
  linux-headers-5.4.0-40 linux-headers-5.4.0-40-generic linux-headers-5.4.0-42
  linux-headers-5.4.0-42-generic linux-headers-5.4.0-45
  linux-headers-5.4.0-45-generic linux-headers-5.4.0-47
  linux-headers-5.4.0-47-generic linux-headers-5.4.0-48
  linux-headers-5.4.0-48-generic linux-image-5.4.0-40-generic
  linux-image-5.4.0-42-generic linux-image-5.4.0-45-generic
  linux-image-5.4.0-47-generic linux-image-5.4.0-48-generic
  linux-modules-5.4.0-40-generic linux-modules-5.4.0-42-generic
  linux-modules-5.4.0-45-generic linux-modules-5.4.0-47-generic
  linux-modules-5.4.0-48-generic linux-modules-extra-5.4.0-40-generic
  linux-modules-extra-5.4.0-42-generic linux-modules-extra-5.4.0-45-generic
  linux-modules-extra-5.4.0-47-generic linux-modules-extra-5.4.0-48-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  virtualbox virtualbox-qt
Suggested packages:
  vde2 virtualbox-guest-additions-iso
The following packages will be REMOVED:
  virtualbox-6.1
The following NEW packages will be installed:
  virtualbox virtualbox-dkms virtualbox-qt
0 upgraded, 3 newly installed, 1 to remove and 21 not upgraded.
Need to get 0 B/43.8 MB of archives.
After this operation, 38.5 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 623364 files and directories currently installed.)
Removing virtualbox-6.1 (6.1.16-140961~Ubuntu~eoan) ...
Selecting previously unselected package virtualbox-dkms.
(Reading database ... 622617 files and directories currently installed.)
Preparing to unpack .../virtualbox-dkms_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb ...
Unpacking virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) ...
Selecting previously unselected package virtualbox.
Preparing to unpack .../virtualbox_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb ...
Unpacking virtualbox (6.1.10-dfsg-1~ubuntu1.20.04.1) ...
Selecting previously unselected package virtualbox-qt.
Preparing to unpack .../virtualbox-qt_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb ...
Unpacking virtualbox-qt (6.1.10-dfsg-1~ubuntu1.20.04.1) ...
Setting up virtualbox (6.1.10-dfsg-1~ubuntu1.20.04.1) ...
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 Thu 2020-11-12 02:50:58 EST; 4ms ago
       Docs: man:systemd-sysv-generator(8)
    Process: 38404 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Nov 12 02:50:58 bucky2 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Nov 12 02:50:58 bucky2 virtualbox[38404]:  * Loading VirtualBox kernel modules...
Nov 12 02:50:58 bucky2 virtualbox[38404]:  * No suitable module for running kernel found
Nov 12 02:50:58 bucky2 virtualbox[38404]:    ...fail!
Nov 12 02:50:58 bucky2 systemd[1]: virtualbox.service: Control process exited, code=exited, status=1/FAILURE
Nov 12 02:50:58 bucky2 systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Nov 12 02:50:58 bucky2 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Setting up virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) ...
Loading new virtualbox-6.1.10 DKMS files...
Building for 5.4.0-52-generic
Building initial module for 5.4.0-52-generic
This system doesn't support Secure Boot
Secure Boot not enabled on this system.
Done.

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

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

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

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 Thu 2020-11-12 02:51:07 EST; 4ms ago
       Docs: man:systemd-sysv-generator(8)
    Process: 41028 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Nov 12 02:51:07 bucky2 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Nov 12 02:51:07 bucky2 virtualbox[41028]:  * Loading VirtualBox kernel modules...
Nov 12 02:51:07 bucky2 virtualbox[41028]:  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
Nov 12 02:51:07 bucky2 virtualbox[41028]:    ...fail!
Nov 12 02:51:07 bucky2 systemd[1]: virtualbox.service: Control process exited, code=exited, status=1/FAILURE
Nov 12 02:51:07 bucky2 systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Nov 12 02:51:07 bucky2 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Setting up virtualbox-qt (6.1.10-dfsg-1~ubuntu1.20.04.1) ...
Processing triggers for desktop-file-utils (0.24+linuxmint1) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for systemd (245.4-4ubuntu3.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for shared-mime-info (1.15-1) ...
bucky2@bucky2:~$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
bucky2@bucky2:~$ sudo modprobe vboxnetflt
modprobe: ERROR: could not insert 'vboxnetflt': Operation not permitted
bucky2@bucky2:~$ 

It didn't work. <EDIT: It DID WORK, see following posts>