You are not logged in.
Hi all,
Last year I have installed VirtualBox with the virtualbox package.
Also another packages:
virtualbox-additions
virtualbox-modules
virtualbox-source
Also has added vboxdrv to the MODULES in /etc/rc.conf.
I made installation under article which now is "out of date".
All works perfectly, one confuses me. When there is a new version of the virtualbox I execute a "vboxbuild".
Here result:
# vboxbuild
:: Unloading VirtualBox kernel modules [DONE]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Recompiling VirtualBox kernel modules (3.2.5-1-ARCH) [DONE]
:: Reloading VirtualBox kernel modules [DONE]
Why they are not removed? How to remove them?
Maybe simply remove them from a folder /lib/modules?
ls /lib/modules
3.0-ARCH 3.1.9-1-ARCH 3.1.9-2-ARCH 3.2.5-1-ARCH extramodules-3.2-ARCH
Sorry for my english.
Thanks
Last edited by Luyan (2012-02-09 09:54:44)
Offline
As far as I'm aware, vboxbuild is no longer necessary if you are installing from the repositories. virtualbox-archlinux-modules from the community repository should contain the modules for the current kernel. Adding them to /etc/rc.conf should be all that you need to do after installing with pacman (or modprobe vboxdrv to add it manually).
As for why the old modules aren't removed, I'll leave that to more experienced users to answer. I don't know. But keep in mind, those folders contain other modules too! Not just vboxdrv and vboxnetflt. If Virtualbox is running that means the correct drivers have been loaded, so there is no harm in leaving them there for now.
διπλοῦν ὁρῶσιν οἱ μαθόντες γράμματα.
Offline
Thanks for the answer. I have reinstalled virtualbox and now there is no necessity for "vboxbuild".
Offline
Note that you do have to run "vboxbuild" if you are running a custom kernel. By doing so, I get the "fail" error mentioned in the first post. So, back to the original question, anybody know how to safely remove the old virtualbox kernels? Or can I just continue to ignore since it works?
May you live all the days of your life.
- Jonathan Swift
Offline
I modified vboxbuild to be more verbose and got this
:: Removing all old VirtualBox kernel modules [BUSY]
rmdir: failed to remove `/lib/modules/3.0-ARCH/extramodules': No such file or directory
rmdir: failed to remove `2': No such file or directory
[FAIL]
:: Removing all old VirtualBox kernel modules [BUSY]
rmdir: failed to remove `/lib/modules/3.0-pae/extramodules': No such file or directory
rmdir: failed to remove `2': No such file or directory
[FAIL]
:: Recompiling VirtualBox kernel modules (3.2.7-1-ARCH) [DONE]
for some reason it's looking in linux 3.0 and not 3.2
Yep, I'm a diaperfur now, I guess
while :;do if windows sucks;then mv windows /dev/null;pacman -Sy linux;fi;done
for i in {\ metal,core,grind};do echo death$i rules\!;done
Offline
Personally I usually just ignore it on the basis that the old modules are sitting in a, now unused, lib/modules/x.x directory now anyway.
Last edited by Roken (2012-02-28 10:46:45)
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline