1 |
On 2/4/21 5:17 PM, Jack wrote: |
2 |
> On 2/4/21 10:10 AM, n952162 wrote: |
3 |
>> On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote: |
4 |
>>> On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote: |
5 |
>>>> The VirtualBox kernel modules do not match this version of VirtualBox. |
6 |
>>> Whenever you update app-emulation/virtualbox *or* your kernel version, |
7 |
>>> you need to update app-emulation/virtualbox-modules as well. The |
8 |
>>> versions of those two packages have to be lock-step, and the latter |
9 |
>>> needs to be rebuilt whenever your kernel version changes, or else the |
10 |
>>> previously-built modules will not load. |
11 |
>>> |
12 |
>> |
13 |
>> Both are in my world file: |
14 |
>> |
15 |
>> # grep virtualbox /var/lib/portage/world |
16 |
>> app-emulation/virtualbox |
17 |
>> app-emulation/virtualbox-modules |
18 |
> |
19 |
> If you have already run virtualbox since the last reboot, you might |
20 |
> need to rmmod those modules to unload the older version. Then you can |
21 |
> use modprobe to load the new versions, without having to reboot. |
22 |
> |
23 |
> Jack |
24 |
> |
25 |
> |
26 |
|
27 |
Good tip, unfortunately, it didn't help: |
28 |
|
29 |
$ sudo rmmod vboxnetadp vboxnetflt vboxdrv |
30 |
Password: |
31 |
$ lsmod | grep vbox |
32 |
$ startvm txm1.4-new |
33 |
WARNING: The vboxdrv kernel module is not loaded. Either there is no module |
34 |
available for the current kernel (4.19.86-gentoo-x86_64) or it |
35 |
failed to |
36 |
load. Please recompile the kernel module and install it by |
37 |
|
38 |
for m in vbox{drv,netadp,netflt}; do modprobe $m; done |
39 |
|
40 |
You will not be able to start VMs until this problem is fixed. |
41 |
Waiting for VM "txm1.4-new" to power on... |
42 |
VBoxManage: error: The virtual machine 'txm1.4-new' has terminated |
43 |
unexpectedly during startup with exit code 1 (0x1) |
44 |
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), |
45 |
component MachineWrap, interface IMachine |
46 |
|
47 |
That takes away my confidence that it would work after a re-boot ... |