On 2/4/21 11:37 AM, n952162 wrote:
On 2/4/21 5:17 PM, Jack wrote:
On 2/4/21 10:10 AM, n952162 wrote:
On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote:
On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote:
The VirtualBox kernel modules do not match this version of
VirtualBox.
Whenever you update app-emulation/virtualbox *or* your kernel version,
you need to update app-emulation/virtualbox-modules as well. The
versions of those two packages have to be lock-step, and the latter
needs to be rebuilt whenever your kernel version changes, or else the
previously-built modules will not load.
Both are in my world file:
# grep virtualbox /var/lib/portage/world
app-emulation/virtualbox
app-emulation/virtualbox-modules
If you have already run virtualbox since the last reboot, you might
need to rmmod those modules to unload the older version. Then you can
use modprobe to load the new versions, without having to reboot.
Jack
Good tip, unfortunately, it didn't help:
$ sudo rmmod vboxnetadp vboxnetflt vboxdrv
Password:
$ lsmod | grep vbox
$ startvm txm1.4-new
WARNING: The vboxdrv kernel module is not loaded. Either there is no
module
available for the current kernel (4.19.86-gentoo-x86_64) or it
failed to
load. Please recompile the kernel module and install it by
for m in vbox{drv,netadp,netflt}; do modprobe $m; done
You will not be able to start VMs until this problem is fixed.
Waiting for VM "txm1.4-new" to power on...
VBoxManage: error: The virtual machine 'txm1.4-new' has terminated
unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component MachineWrap, interface IMachine
That takes away my confidence that it would work after a re-boot ...
You did an rmmod, but I don't see that you loaded the new modules - the
modprobe part. It is possible that they do not get loaded automatically
on demand, but only at boot time, so a manual load should work.
