Opened 5 years ago
Last modified 5 years ago
#18770 new defect
can't use VirtualBox under debian-live-10.0.0-amd64-kde
| Reported by: | beta_tester | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.0.10 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Linux |
Description
hello, i just made a fresh installation of debian-live-10.0.0-amd64-kde.iso to my harddisk and i tried to install virtualbox.
i followed the instruction on Debian-based Linux distributions
:~$ echo "deb https://download.virtualbox.org/virtualbox/debian buster contrib" | sudo tee -a /etc/apt/sources.list.d/virtualbox.list :~$ wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add - :~$ sudo apt update -y Hit:1 http://security.debian.org/debian-security buster/updates InRelease Hit:2 https://download.virtualbox.org/virtualbox/debian buster InRelease Hit:3 http://deb.debian.org/debian buster InRelease Hit:4 http://deb.debian.org/debian buster-updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. :~$ apt search virtualbox ... virtualbox-5.2/unknown 5.2.32-132073~Ubuntu~bionic amd64 Oracle VM VirtualBox virtualbox-6.0/unknown 6.0.10-132072~Ubuntu~bionic amd64 Oracle VM VirtualBox ... :~$ sudo apt install virtualbox-6.0 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libcurl4 libsdl-ttf2.0-0 linux-headers-amd64 Recommended packages: linux-image The following NEW packages will be installed: libcurl4 libsdl-ttf2.0-0 linux-headers-amd64 virtualbox-6.0 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 103 MB of archives. After this operation, 228 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian buster/main amd64 libcurl4 amd64 7.64.0-4 [332 kB] Get:2 http://deb.debian.org/debian buster/main amd64 libsdl-ttf2.0-0 amd64 2.0.11-6 [18,6 kB] Get:3 http://deb.debian.org/debian buster/main amd64 linux-headers-amd64 amd64 4.19+105 [6.652 B] Get:4 https://download.virtualbox.org/virtualbox/debian buster/contrib amd64 virtualbox-6.0 amd64 6.0.10-132072~Ubuntu~bionic [102 MB] Fetched 103 MB in 30s (3.424 kB/s) ...
i was wondering that during installation the virtualbox packet it was shown "6.0.10-132072~Ubuntu~bionic", but i am on an debian environment at that moment
ok, so far so good... virtualbox starts as normal as i expected.
but when i create a new virtual machine and start it, i get an error message.
Failed to open a session for the virtual machine Test.
The virtual machine 'Test' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
the same error message i get, when i add an existing virtual machine i created and used earlier under Ubuntu19.04.
the current installed version under Debian Buster (KDE) shows: Version 6.0.10 r132072 (Qt5.11.3)
Change History (8)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
See #11577. It was supposed to be fixed for Ubuntu and Debian, but it was ... broken. The changes that are required to address it are in Comment:15, https://www.virtualbox.org/ticket/11577#comment:15
comment:3 by , 5 years ago
thank you for the link... does it mean, i have to compile and sign virtualbox module by myself and import the sign-key to UEFI? i am not allowed to change any UEFI/BIOS settings on that computer...
comment:4 by , 5 years ago
In theory, if you apply the patch, you won't have to sign them yourself, they will be signed using the already existing certificates (that's my understanding at least). Read ticket #11577 from the beginning...
comment:5 by , 5 years ago
when i apply the patch of #11577 comment 15 to /usr/lib/virtualbox/vboxdrv.sh and execute vboxconfig,
i get this output:
:~$ sudo /sbin/vboxconfig vboxdrv.sh: Stopping VirtualBox services. vboxdrv.sh: Starting VirtualBox services. vboxdrv.sh: You must sign these kernel modules before using VirtualBox: vboxdrv vboxnetflt vboxnetadp vboxpci See the documenatation for your Linux distribution.. vboxdrv.sh: Building VirtualBox kernel modules. modinfo: ERROR: Module vboxdrv not found. /usr/lib/virtualbox/vboxdrv.sh: 491: /usr/lib/virtualbox/vboxdrv.sh: /usr/src/kernels/4.19.0-5-amd64/scripts/sign-file: not found modinfo: ERROR: Module vboxnetflt not found. /usr/lib/virtualbox/vboxdrv.sh: 492: /usr/lib/virtualbox/vboxdrv.sh: /usr/src/kernels/4.19.0-5-amd64/scripts/sign-file: not found modinfo: ERROR: Module vboxnetadp not found. /usr/lib/virtualbox/vboxdrv.sh: 493: /usr/lib/virtualbox/vboxdrv.sh: /usr/src/kernels/4.19.0-5-amd64/scripts/sign-file: not found modinfo: ERROR: Module vboxpci not found. /usr/lib/virtualbox/vboxdrv.sh: 494: /usr/lib/virtualbox/vboxdrv.sh: /usr/src/kernels/4.19.0-5-amd64/scripts/sign-file: not found No DKMS packages installed: not changing Secure Boot validation state. vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why. There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. If your system is using EFI Secure Boot you may need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
and:
:~$ sudo dmesg ... [ 843.814318] Lockdown: Loading of unsigned modules is restricted; see https://wiki.debian.org/SecureBoot
comment:6 by , 5 years ago
what else can i try to get virtualbox working under Debian 10 + UEFI + SecureBoot, without touching UEFI/BIOS settings of the computer and without selfsigning/compiling virtualbox/modules?
why isn't there a virtualbox package available in the Debian Buster repository itself?
comment:7 by , 5 years ago
Hi,
On Debian 'sign-file' doesn't seem to be placed in '/usr/src/kernels/.../scripts/' but rather in '/usr/src/linux-headers-.../scripts/'
So you should try to modify the patch by replacing '/usr/src/kernels/$(uname -r)/scripts/sign-file' with '/usr/src/linux-headers-$(uname -r)/scripts/sign-file'
comment:8 by , 5 years ago
right, on LinxMint (as an Ubuntu/Debian derivate) I get
fbatschu@minibox:/$ ls -la /usr/src/kernels/$(uname -r)/scripts/sign-file ls: cannot access '/usr/src/kernels/4.15.0-55-generic/scripts/sign-file': No such file or directory
fbatschu@minibox:/$ ls -la /usr/src/linux-headers-$(uname -r)/scripts/sign-file -rwxr-xr-x 1 root root 18752 Jul 2 18:41 /usr/src/linux-headers-4.15.0-55-generic/scripts/sign-file
Linux minibox 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
fbatschu@minibox:/$ cat /etc/os-release NAME="Linux Mint" VERSION="19 (Tara)" ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME="Linux Mint 19" VERSION_ID="19" HOME_URL="https://www.linuxmint.com/" SUPPORT_URL="https://forums.ubuntu.com/" BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/" PRIVACY_POLICY_URL="https://www.linuxmint.com/" VERSION_CODENAME=tara UBUNTU_CODENAME=bionic
i ran virtualbox from a console and here some additional information:
:~$ virtualbox WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (4.19.0-5-amd64) 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. :~$ sudo vboxconfig vboxdrv.sh: Stopping VirtualBox services. vboxdrv.sh: Starting VirtualBox services. vboxdrv.sh: You must sign these kernel modules before using VirtualBox: vboxdrv vboxnetflt vboxnetadp vboxpci See the documenatation for your Linux distribution..is it possible, that it is, because Debian Buster is installed on a system with UEFI + SecureBoot enabled? under buntu 19.04 it wasn't an issue... but there i used the virtualbox package directly from the ubuntu repository. on Debian Buster, there is no virtualbox package directly available.