| 1 |
On Thursday, 4 February 2021 16:37:01 GMT 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 VirtualBox. |
| 7 |
> >>> |
| 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 |
> >> Both are in my world file: |
| 15 |
> >> |
| 16 |
> >> # grep virtualbox /var/lib/portage/world |
| 17 |
> >> app-emulation/virtualbox |
| 18 |
> >> app-emulation/virtualbox-modules |
| 19 |
> > |
| 20 |
> > If you have already run virtualbox since the last reboot, you might |
| 21 |
> > need to rmmod those modules to unload the older version. Then you can |
| 22 |
> > use modprobe to load the new versions, without having to reboot. |
| 23 |
> > |
| 24 |
> > Jack |
| 25 |
> |
| 26 |
> Good tip, unfortunately, it didn't help: |
| 27 |
> |
| 28 |
> $ sudo rmmod vboxnetadp vboxnetflt vboxdrv |
| 29 |
> Password: |
| 30 |
> $ lsmod | grep vbox |
| 31 |
> $ startvm txm1.4-new |
| 32 |
> WARNING: The vboxdrv kernel module is not loaded. Either there is no module |
| 33 |
> available for the current kernel (4.19.86-gentoo-x86_64) or it |
| 34 |
> failed to |
| 35 |
> load. Please recompile the kernel module and install it by |
| 36 |
> |
| 37 |
> for m in vbox{drv,netadp,netflt}; do modprobe $m; done |
| 38 |
> |
| 39 |
> You will not be able to start VMs until this problem is fixed. |
| 40 |
> Waiting for VM "txm1.4-new" to power on... |
| 41 |
> VBoxManage: error: The virtual machine 'txm1.4-new' has terminated |
| 42 |
> unexpectedly during startup with exit code 1 (0x1) |
| 43 |
> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), |
| 44 |
> component MachineWrap, interface IMachine |
| 45 |
> |
| 46 |
> That takes away my confidence that it would work after a re-boot ... |
| 47 |
|
| 48 |
Try again updating the modules, but use the correct syntax. The prefix "@" |
| 49 |
denotes this is a predefined set and it will rebuild any packages which own |
| 50 |
files in your /lib/modules: |
| 51 |
|
| 52 |
emerge -1aDv @module-rebuild |
| 53 |
|
| 54 |
I assume you have already installed 'app-emulation/virtualbox-modules' at |
| 55 |
least once, if VBox was working OK until recently? Otherwise, emerge the |
| 56 |
package 'app-emulation/virtualbox-modules' and modprobe each module keeping an |
| 57 |
eye in dmesg to make sure they load without further errors. |
Archives