Cómo instalar VirtualBox en e16 la versión de 64 bits?

Hola, buenas tardes

He intentado instalar virtualbox en la e16 de 64 bits. Lo necesito para poder trabajar con Power Bi, no quiero usar Windows 11. Desde la consola usando y también el paquete virtualbox-7.1_7.1.12-169651~Debian~bookworm_amd64.deb ( el cual se indica que todas las dependencias están satisfechas), sin embargo al momento de instalar arroja este error:
(Leyendo la base de datos ... 315394 ficheros o directorios instalados actualmente.)
Desinstalando virtualbox-7.1 (7.1.12-169651~Debian~bookworm) ...
Procesando disparadores para libc-bin (2.36-9+deb12u10) ...
Procesando disparadores para shared-mime-info (2.2-1) ...
Procesando disparadores para hicolor-icon-theme (0.17-2) ...
Procesando disparadores para desktop-file-utils (0.26-1) ...
Procesando disparadores para mailcap (3.70+nmu1) ...
Seleccionando el paquete virtualbox-7.1 previamente no seleccionado.
(Leyendo la base de datos ... 314634 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar .../virtualbox-7.1_7.1.12-169651~Debian~bookworm_amd64.deb ...
Desempaquetando virtualbox-7.1 (7.1.12-169651~Debian~bookworm) ...
Configurando virtualbox-7.1 (7.1.12-169651~Debian~bookworm) ...
addgroup: El grupo `vboxusers' ya existe como grupo del sistema. Saliendo.
libkmod: ERROR ../libkmod/libkmod-config.c:772 conf_files_filter_out: Directories inside directories are not supported: /etc/modprobe.d/virtualbox-dkms.conf
libkmod: ERROR ../libkmod/libkmod-config.c:772 conf_files_filter_out: Directories inside directories are not supported: /etc/modprobe.d/virtualbox-dkms.conf
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
linux-headers-amd64 linux-headers-6.11.5+bpo-amd64
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
linux-headers-amd64 linux-headers-6.11.5+bpo-amd64

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.
Procesando disparadores para libc-bin (2.36-9+deb12u10) ...
Procesando disparadores para desktop-file-utils (0.26-1) ...
Procesando disparadores para mailcap (3.70+nmu1) ...
Procesando disparadores para hicolor-icon-theme (0.17-2) ...
Procesando disparadores para shared-mime-info (2.2-1) ...

Entiendo que faltaban los linux-headers, sin embargo no encontré los adecuados para el kernel he instale el linux-headers-generic, no dando solución.

Este es el Kernel que tengo instalado:

~ ❯❯❯ uname -r
6.11.5+bpo-amd64
~ ❯❯❯

De antemano agradezco su tiempo y ayuda.

Saludos,

Might as well upgrade the kernel while you're at it (currently 6.12.38) and the headers as well as virtualbox-dkms. ... and use the virtualbox from the Elive repositories (virtualbox/bookworm,now 7.1.12-dfsg-2 amd64) :innocent:

apui linux-image-amd64 linux-headers-amd64 virtualbox-qt virtualbox-dkms

Reboot the machine into your new kernel and run virtualbox. :happybounce:

Note:
When using i.e "apug" it will now automagically want to upgrade your kernel (linux-image) but not necessarily 'linux-headers'. So either stick to the working kernel you just installed or upgrade the headers manually too.

1 Like

Muchas gracias Triantares, me ha servido tu ayuda.
Consulta, qué hago con el kernel antiguo? Lo desinstalo ?

Saludos.

You can once you're sure you don't need it anymore and don't want it in your grub boot-screen as an option either.

What I do is remove old ones very specifically as in your case i.e

apr --purge linux-image-6.11.5*

But be very careful which kernel/image you remove because if you accidentally remove all your working kernels you will be left with an un-bootable system. :shocked:

Muchas gracias.

Saludos,

Error for me on Elive 3.8.50:E: /var/cache/apt/archives/linux-image-6.12.38+deb12-amd64_6.12.38-1~bpo12+1_amd64.deb: Unable to copy extracted data for './lib/modules/6.12.38+deb12-amd64/kernel/drivers/w1/wire.ko.xz' to '/lib/modules/6.12.38+deb12-amd64/kernel/drivers/w1/wire.ko.xz.dpkg-new': Unexpected end of file or stream

Looks like a download error to me. Could be corrupted data, the repo itself or even a full HD.:thinking:
I've got that kernel running just fine.

What does apse linux-headers |grep 6.12.38 give?

apse linux-headers |grep 6.12.38

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

linux-headers-6.12.38+deb12-amd64/oldstable-backports 6.12.38-1~bpo12+1 amd64
Header files for Linux 6.12.38+deb12-amd64
linux-headers-6.12.38+deb12-cloud-amd64/oldstable-backports 6.12.38-1~bpo12+1 amd64
Header files for Linux 6.12.38+deb12-cloud-amd64
linux-headers-6.12.38+deb12-common/oldstable-backports,oldstable-backports 6.12.38-1~bpo12+1 all
Common header files for Linux 6.12.38+deb12
linux-headers-6.12.38+deb12-common-rt/oldstable-backports,oldstable-backports 6.12.38-1~bpo12+1 all
Common header files for Linux 6.12.38+deb12-rt
linux-headers-6.12.38+deb12-rt-amd64/oldstable-backports 6.12.38-1~bpo12+1 amd64
Header files for Linux 6.12.38+deb12-rt-amd64
linux-headers-amd64/oldstable-backports,now 6.12.38-1~bpo12+1 amd64 [configuration restante]
linux-headers-cloud-amd64/oldstable-backports 6.12.38-1~bpo12+1 amd64
linux-headers-rt-amd64/oldstable-backports 6.12.38-1~bpo12+1 amd64

That's indeed the problem you stated.

You can try to install the headers again with apui linux-headers-amd64 or ...
sudo apt-install -r to 'repair' a situation.

Btw, did the 'linux-image-amd64' install as it should?
That would be the output of:
dpkg -l |grep linux-image

sudo apt-get autoremove

Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Les paquets suivants seront ENLEVÉS :
linux-headers-6.12.38+deb12-common linux-kbuild-6.12.38+deb12 pahole
0 mis à jour, 0 nouvellement installés, 3 à enlever et 0 non mis à jour.
Après cette opération, 66,7 Mo d'espace disque seront libérés.

sudo apt-install -r
[sudo] triki's password:
sudo: apt-install: command not found

apui linux-headers-amd64

Dépaquetage de linux-image-6.12.38+deb12-amd64 (6.12.38-1~bpo12+1) ...
dpkg-deb (sous-processus) : décompression de l'archive « /tmp/apt-dpkg-install-3bnbcd/0-linux-image-6.12.38+deb12-amd64_6.12.38-1~bpo12+1_amd64.deb » (taille=107766092) membre « data.tar » : erreur LZMA : les données compressées sont corrompues
dpkg-deb: erreur: le sous-processus a renvoyé un état de sortie d'erreur 2
dpkg: erreur de traitement de l'archive /tmp/apt-dpkg-install-3bnbcd/0-linux-image-6.12.38+deb12-amd64_6.12.38-1~bpo12+1_amd64.deb (--unpack) :
impossible de copier les données extraites pour « ./lib/modules/6.12.38+deb12-amd64/kernel/drivers/w1/wire.ko.xz » vers « /lib/modules/6.12.38+deb12-amd64/kernel/drivers/w1/wire.ko.xz.dpkg-new » : fin de fichier ou de flux inattendue
Sélection du paquet linux-headers-6.12.38+deb12-common précédemment désélectionné.
Préparation du dépaquetage de .../1-linux-headers-6.12.38+deb12-common_6.12.38-1~bpo12+1_all.deb ...

dpkg -l |grep linux-image 100
ii linux-image-6.11.10+bpo-amd64 6.11.10-1~bpo12+1 amd64 Linux 6.11 for 64-bit PCs (signed)
rc linux-image-amd64 6.12.38-1~bpo12+1 amd64 Linux for 64-bit PCs (meta-package)

My bad, that should've been:
sudo apt -f install or simply: apif

There it is. Maybe just wait out until it gets fixed or google it see if it's known bug.

The r in 'rc' here means it is set to be removed and the c stands for config files but I'm not sure what that means exactly in this case. :thinking:
One thing is for sure is that you're not running 6.12.38 nor is it set to be installed.
Maybe just purge 6.12.38 and install it again ..... just the kernel i.e api linux-image-amd64 and see if that will work out.
If it does install (it should be marked 'ii'), then (re)boot into 6.12.38 and install the headers and virtualbox as mentioned before.

Ok I'll try. Thanks.

ALL GOOD!
On my brand new installation it works. Thank you.
Generating grub configuration file ...

Found theme: /boot/grub/themes/elive-dark/theme.txt
Found background image: .background_cache.png
Found linux image: /boot/vmlinuz-6.12.38+deb12-amd64
Found initrd image: /boot/initrd.img-6.12.38+deb12-amd64
Found linux image: /boot/vmlinuz-6.11.10+bpo-amd64
Found initrd image: /boot/initrd.img-6.11.10+bpo-amd64
Found linux image: /boot/vmlinuz-6.11.10+bpo-amd64
Found initrd image: /boot/initrd.img-6.11.10+bpo-amd64
Found linux image: /boot/vmlinuz-6.12.38+deb12-amd64
Found initrd image: /boot/initrd.img-6.12.38+deb12-amd64
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done
Paramétrage de linux-image-amd64 (6.12.38-1~bpo12+1) .

the config remains installed on /etc, to remove fully you need to add --purge

warning, don't use the 6.12 if your disk is on btrfs, better to use 6.11

I was being a bit cagey on that, considering the rather weird errors that were thrown up there.

I wasn't sure about what happened in previous attempts and/or whether this was solely about installing the kernel or installing virtualbox-dkms too. :innocent:

1 Like