On 2/4/21 6:36 PM, Michael wrote:
On Thursday, 4 February 2021 17:25:35 GMT n952162 wrote:
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".
Oops! My apologies - I was running from apparently faulty memory! :-)
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 ;-)
OK, as long as the VBox modules were rebuilt after the new kernel symlink was
set under /usr/src/linux they should (re)load after a reboot.
Loading modules manually requires you run modprobe as root.
However, you do not need to start VBox as root, arguably you shouldn't. Just
make sure your user is a member of group "vboxusers":
# gpasswd -a <user> vboxusers
Logout/in as the named user before you can run VBox again.
More info you should need it can be found here:
https://wiki.gentoo.org/wiki/VirtualBox
Well, what's not exactly clear to me is whether the vbox modules are
preloaded at boot (i.e. as root) ... it must be that, because vboxmanage
doesn't run setuid:
$ ls -lL $(type -p vboxmanage)
-rwxr-x--- 1 root vboxusers 3570 Feb 3 02:50 /usr/bin/vboxmanage
So that was a mistaken assumption I'd had, that the modules would be
loaded on demand. Too bad, actually.
