Install virtualbox on Ubuntu with UEFI Secure boot

https://askubuntu.com/a/768310

 

 

 ┌────────────────────────────────────────────────────────────┤ Configuring Secure Boot ├────────────────────────────────────────────────────────────┐  
 │                                                                                                                                                   │  
 │ Your system has UEFI Secure Boot enabled.                                                                                                         │  
 │                                                                                                                                                   │  
 │ UEFI Secure Boot is not compatible with the use of third-party drivers.                                                                           │  
 │                                                                                                                                                   │  
 │ The system will assist you in toggling UEFI Secure Boot. To ensure that this change is being made by you as an authorized user, and not by an     │  
 │ attacker, you must choose a password now and then use the same password after reboot to confirm the change.                                       │  
 │                                                                                                                                                   │  
 │ If you choose to proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but the Secure Boot state  │  
 │ will not be changed.                                                                                                                              │  
 │                                                                                                                                                   │  
 │ If Secure Boot remains enabled on your system, your system may still boot but any hardware that requires third-party drivers to work correctly    │  
 │ may not be usable.                                                                                                                                │  
 │

e.g.

 

Setting up virtualbox (5.1.38-dfsg-0ubuntu1.16.04.2) …
vboxweb.service is a disabled or a static unit, not starting it.
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; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-01-29 15:51:32 GMT; 2ms ago
Docs: man:systemd-sysv-generator(8)
Process: 10816 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Jan 29 15:51:32 w-dell systemd[1]: Starting LSB: VirtualBox Linux kernel module…
Jan 29 15:51:32 w-dell virtualbox[10816]: * Loading VirtualBox kernel modules…
Jan 29 15:51:32 w-dell virtualbox[10816]: * modprobe vboxdrv failed. Please use ‘dmesg’ to find out why
Jan 29 15:51:32 w-dell virtualbox[10816]: …fail!
Jan 29 15:51:32 w-dell systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Jan 29 15:51:32 w-dell systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Jan 29 15:51:32 w-dell systemd[1]: virtualbox.service: Unit entered failed state.
Jan 29 15:51:32 w-dell systemd[1]: virtualbox.service: Failed with result ‘exit-code’.
Setting up virtualbox-qt (5.1.38-dfsg-0ubuntu1.16.04.2) …
Processing triggers for libc-bin (2.23-0ubuntu10) …
Processing triggers for shim-signed (1.33.1~16.04.3+15+1533136590.3beb971-0ubuntu1) …
Processing triggers for systemd (229-4ubuntu21.15) …
Processing triggers for ureadahead (0.100.0-19) …
W: Operation was interrupted before it could finish

Leave a Reply

Your email address will not be published. Required fields are marked *