On 2/4/21 5:56 PM, Michael wrote:
On Thursday, 4 February 2021 16:37:01 GMT 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 ...
Try again updating the modules, but use the correct syntax. The prefix "@"
denotes this is a predefined set and it will rebuild any packages which own
files in your /lib/modules:
emerge -1aDv @module-rebuild
???
Sorry, if I gave the impression, when I said:
/I tried that (using "module-rebuild")/
that I ran it without the "@". I was just referring to the original
suggestion had "@module*s*-rebuild".
Did you run on the host, after you updated your VBox:
emerge -uaDv @modules-rebuild
In fact, it had emerged successfully:
...
[ebuild U ] sys-libs/timezone-data-2020e::gentoo
[2020d::gentoo] USE="nls -leaps-timezone -zic-slim" 659 KiB
[ebuild U ] app-eselect/eselect-pinentry-0.7.1::gentoo
[0.7::gentoo] 0 KiB
[ebuild U ] virtual/perl-Data-Dumper-2.174.0-r2::gentoo
[2.174.0-r1::gentoo] 0 KiB
[ebuild NS ] sys-kernel/gentoo-sources-5.4.92:5.4.92::gentoo
[4.19.86:4.19.86::gentoo, 5.4.38:5.4.38::gentoo,
5.4.66:5.4.66::gentoo, 5.4.80-r1:5.4.80-r1::gentoo] USE="-build
-experimental -symlink" 2938 KiB
Total: 4 packages (3 upgrades, 1 in new slot), Size of downloads:
3596 KiB
...
but failed to run.
I assume you have already installed 'app-emulation/virtualbox-modules' at
least once, if VBox was working OK until recently? Otherwise, emerge the
package 'app-emulation/virtualbox-modules' and modprobe each module keeping an
eye in dmesg to make sure they load without further errors.
I followed this advice, to load each module (from equery files
virtualbox-modules) by hand, and that worked, for whatever reason that
it didn't work before after unloading the modules by hand, as
recommended by Jack ... they were not loaded when I just loaded them now
... ah - naturally, I loaded them with sudo, but didn't use sudo when I
ran startvm ... Hmmm. We'll see how it starts up tomorrow ;-)
