You are not logged in.
I have installed:
community/virtualbox 4.2.18-2
community/virtualbox-guest-iso 4.2.18-1
community/virtualbox-host-modules 4.2.18-4
After last update VirtualBox stopped working.
# modprobe -v vboxdrv
insmod /lib/modules/3.11.3-1-ARCH/extramodules/vboxdrv.ko.gz
modprobe: ERROR: could not insert 'vboxdrv': Invalid argument
What should I do?
Offline
You should always state exactly what was updated, as otherwise it will be guesswork for anyone trying to help you. So for most cases, the first you should do is look at what was updated.
However, I'm going to make a little guess here that among whatever else was updated, your kernel was updated. The virtualbox modules for the 3.11.3 kernel are in testing at the moment. So if my guess is correct, then you can simply wait for the modules to come into community repo, and then update.
Offline
I suspect uname -a and pacman -Q linux return different version numbers. If so, reboot.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
The problem is real.
sudo modprobe vboxdrv
[sudo] password for uzer:
modprobe: ERROR: could not insert 'vboxdrv': Invalid argument
$ uname -a
Linux mainland 3.11.3-1-ARCH #1 SMP PREEMPT Wed Oct 2 01:38:48 CEST 2013 x86_64 GNU/Linux
$ pacman -Q linux
linux 3.11.3-1
Latest linux probably broke it.
Last edited by 89c51 (2013-10-05 16:15:33)
Offline
I suspect uname -a and pacman -Q linux return different version numbers. If so, reboot.
Nope. They are the same. (At least for me). I'm having the same issue after the kernel update to 3.11.3.
Last edited by Shinto (2013-10-05 16:15:37)
Offline
Odd, it must also depend on something else, as I just updated to 3.11 and have no problem with virtualbox.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
https://projects.archlinux.org/svntogit … 4c619a43dc states it is a rebuild for 3.11.3, so I simple assumed that's the reason the virtualbox modules will not load. It has always been like this in the past, that I would need updated virtualbox modules after pretty much all kernel updates.
Trilby, are you using the host module sources? I know you can have it automatically recompile the modules on kernel updates.
Offline
I don't know much about virtualization. I have virtualbox and virtualbox-host-modules installed from [community] with no custom setup or configuration and no recompiling. Modprobing vboxdrv worked without issue (once I rebooted to the new kernel), and my winXP guest system is running as we speak.
This is on my i686 system, I don't know if that'd be relevant.
Last edited by Trilby (2013-10-05 17:36:06)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
The virtualbox host modules for the new kernel (3.11.3) haven't been pushed to community yet, just enable [testing], update and everything should work just fine.
Offline
Trilby, I don't know that much either, just going by what I've read in the wiki and past experiences. I have x86_64, so maybe that makes some difference. In any case, I am unable to to load vboxdrv with the same problem as noted by others in this thread.
As for demyze's suggestion, it should perhaps be noted that by no means should people activate testing and update their whole system (unless they really want to do that, of course), just the virtualbox modules in question should fix it. Personally I am quite content to let this wait until the package is released to community repo.
Offline
I have the same problem... would enabling testing and upgrading vboxdrv , and immediately disabling testing be safe?
How long till the package gets out of testing ?
EDIT:
upgraded - no issues.
Last edited by SilverOne (2013-10-05 18:28:23)
Best Regards,
SilverOne
Offline
How long should it take? Just "pacman -Syu" should sufice?
[root@junior junior]# uname -a
Linux junior 3.11.3-1-ARCH #1 SMP PREEMPT Wed Oct 2 01:38:48 CEST 2013 x86_64 GNU/Linux
[root@junior junior]# pacman -Q linux
linux 3.11.3-1
[root@junior junior]#
If it ain't broke, you haven't tweaked it enough...
Offline
How long should it take? Just "pacman -Syu" should sufice?
[root@junior junior]# uname -a Linux junior 3.11.3-1-ARCH #1 SMP PREEMPT Wed Oct 2 01:38:48 CEST 2013 x86_64 GNU/Linux
[root@junior junior]# pacman -Q linux linux 3.11.3-1 [root@junior junior]#
hello, sudo pacman -Syu would update your ENTIRE SYSTEM to testing ....
remove the # from community testing and run:
sudo pacman -S virtualbox-host-modules
then comment back the community testing
Best Regards,
SilverOne
Offline
I'll read more about the testing repo to see if it's 100% safe. Otherwise I'll just wait.
If it ain't broke, you haven't tweaked it enough...
Offline
Read https://bbs.archlinux.org/viewtopic.php … 0#p1333500
You shouldn't use just [community-testing] as these packages rely on the packages from [testing]. You have to uncomment both repos.
Offline
I had the same problem, tried using the "virtualbox-guest-modules" and "virtualbox-host-modules" package from [community-testing] and it worked. The rest of the package is not upgraded (or I should say there is no newer version), so modules like "vboxguest" and "vboxsf" still cannot be loaded (because "virtualbox-guest-utils" has not been upgraded yet").
But at least "vboxdrv", "vboxnetadp", "vboxnetflt" all can be loaded.
Packages installed:
community/virtualbox 4.2.18-2 [インストール済み]
Powerful x86 virtualization for enterprise as well as home use
community/virtualbox-guest-dkms 4.2.18-2 [インストール済み]
VirtualBox Guest kernel modules sources
community/virtualbox-guest-iso 4.2.18-1 [インストール済み]
The official VirtualBox Guest Additions ISO image
community/virtualbox-guest-modules 4.2.18-4 [インストール済み: 4.2.18-6]
Guest kernel modules for VirtualBox
community/virtualbox-guest-utils 4.2.18-2 [インストール済み]
VirtualBox Guest userspace utilities
community/virtualbox-host-dkms 4.2.18-2 [インストール済み]
VirtualBox Host kernel modules sources
community/virtualbox-host-modules 4.2.18-4 [インストール済み: 4.2.18-6]
Host kernel modules for VirtualBox
Last edited by chrlin (2013-10-06 11:51:39)
The Arch Way - The Meaning of System - The Flow of Data - The Layer of Abstraction - The Power of Root - The Law of Command - The Communication of Terminal - The Union of Man and Machine
上之道 - 生之義 - 氣之流 - 天之層 - 活之力 - 命之理 - 靈之通 - 天人合一
Offline
chrlin, when posting on the forum, please prepend your commands with LC_ALL=C so that the output is in English.
Please edit your post so we know what is says.
Also, when posting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.
Offline
what happens when you already have testing and community-testing uncommented and you get this error with Virtualbox kernel modules.
after my last
sudo pacman -Syu
I am now also getting
modprobe: ERROR: could not insert 'vboxdrv': Invalid argument
modprobe: ERROR: could not insert 'vboxnetflt': Invalid argument
this is for
virtualbox 4.3.4-1
virtualbox-host-modules 4.3.4-2
wait for Virtualbox package to get an update or somehow roll back host modules to previous version?
what do?
Last edited by infiniphunk (2013-12-12 03:12:06)
Offline
FWIW, I downgraded from kernel 3.12.4-1 to 3.12.3-1 and the virtualbox modules load again.
community/virtualbox 4.3.4-1
community/virtualbox-guest-iso 4.3.4-1
community-testing/virtualbox-host-modules 4.3.4-2
Offline
It was fine in the end, not even 12 hours later I did an upgrade again and it was fixed.
Offline
I think it might be important to mention at this point that I would hardly call this a problem. It is simply that the vbox modules for a new kernel has not been released into community repo yet. It will probably keep happening on most kernel updates, and there really is nothing more to it than simply waiting for the updated kernel modules to be released from testing.
If waiting is problematic, then you can do it yourself as is explained in the wiki: https://wiki.archlinux.org/index.php/Vi … el_modules
Offline
That's absolutely correct Daerandin. The lesson here is, don't use testing for virtualization if it's going to be mission critical (which in my case here it isn't)
Offline
Is it just me or it's happening again? ¬_¬
If it ain't broke, you haven't tweaked it enough...
Offline
No, not just you, it's really happens again.
See https://bbs.archlinux.org/viewtopic.php … 8#p1456328
Last edited by hb860 (2014-09-15 18:44:44)
Offline
No, not just you, it's really happens again.
See https://bbs.archlinux.org/viewtopic.php … 8#p1456328
Actually I don't think we're talking about the same problem.
Mine is that vboxdrv can't be modprobe-d.
[root@junior ~]# modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found.
If it ain't broke, you haven't tweaked it enough...
Offline