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