You are not logged in.
VirtualBox fails to start giving this message:
Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007) $ lsmod | grep box
vboxpci 14581 0
vboxnetflt 17612 0
vboxnetadp 18323 0
vboxdrv 1823264 3 vboxnetadp,vboxnetflt,vboxpcicommunity/libvirt 1.1.1-2 [installed]
community/virtualbox 4.2.16-1 [installed]
community/virtualbox-ext-vnc 4.2.16-1 [installed]
community/virtualbox-host-dkms 4.2.16-1 [installed]
community/virtualbox-host-modules 4.2.16-8 [installed]So I'm well aware of:
https://bbs.archlinux.org/viewtopic.php?id=165683
and
https://bbs.archlinux.org/viewtopic.php?pid=1304516
and
https://bbs.archlinux.org/viewtopic.php?id=134841
However,
The first one never received a reply, my system is fully up to date, and I do not have testing or community-testing repos enabled:
$ pacman -Qi libpng
Name : libpng
Version : 1.6.3-1pacman -Qi qt4
Name : qt4
Version : 4.8.5-1$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
archlinuxfr is up to date
:: Starting full system upgrade...
there is nothing to do$ sudo dkms install vboxhost/$(pacman -Q virtualbox|awk {'print $2'}|sed 's/\-.\+//') -k $(uname -rm|sed 's/\ /\//')
Module vboxhost/4.2.16 already installed on kernel 3.10.9-1-ARCH/x86_64I followed this wiki page:
https://wiki.archlinux.org/index.php/VirtualBox
Anybody else run into this and solve it?
Last edited by thoth (2013-08-25 21:57:48)
Offline
I had some issues with VirtualBox not starting not too long ago. I started using the git kernel and suddenly it just didn't work at all. So I think what I had to end up doing was moving the actual generated config file out of the way, and letting it regenerate. It should be ~/.VirtualBox/VirtualBox.xml (note that it is a dotfile and not where the actual vitual machine images are stored).
If this works, then you will have to manually add your virtual machines back into VirtualBox (which i my case actually didn't work… but they continued to work with the standard kernel).
Offline
rm -Rf .VirtualBoxdid the trick. Standard kernel, all VMs look to be fine.
Thanks for the sanity check WonderWoofy!
Marking as solved.
Offline
Neato! Glad you got it working.
Offline