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