VBoxManage: error: Failed to create a session object!

Nebu · 2013-10-22 20:55:08

When I run

vagrant up

I get the following output:

Bringing machine 'default' up with 'virtualbox' provider...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["list", "hostonlyifs"]

Stderr: VBoxManage: error: Failed to create a session object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

I tried directly running

VBoxManage list

and I get this output:

VBoxManage: error: Failed to create a session object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

VirtualBox (and vagrant) were both working earlier today, but I updated a bunch of packages via

yaourt -Syua

which I suspect is what caused the problem. Here's (what I think are) the relevant part of

/var/logs/pacman.log

[2013-10-22 15:53] [PACMAN] starting full system upgrade
...
[2013-10-22 15:55] [PACMAN] upgraded libpng (1.6.5-1 -> 1.6.6-1)
...
[2013-10-22 15:55] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-10-22 15:55] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Starting build: 3.11.6-1-ARCH
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Starting build: 3.11.6-1-ARCH
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-10-22 15:55] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-10-22 15:55] [PACMAN] upgraded linux (3.11.5-1 -> 3.11.6-1)
...
[2013-10-22 15:56] [ALPM] warning: /boot/syslinux/syslinux.cfg installed as /boot/syslinux/syslinux.cfg.pacnew
[2013-10-22 15:56] [ALPM-SCRIPTLET] Syslinux BIOS update successful
[2013-10-22 15:56] [ALPM-SCRIPTLET] If you used syslinux-install_update to install syslinux:
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> If you want to use syslinux with menu and all modules please rerun
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==>   # /usr/bin/syslinux-install_update -i -a -m
[2013-10-22 15:56] [ALPM-SCRIPTLET] 
[2013-10-22 15:56] [ALPM-SCRIPTLET] If you manually installed syslinux:
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> Please copy or symlink all .c32 modules to your /boot/syslinux directory.
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> If (/ and /boot on seperate fs):
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==>   # cp /usr/lib/syslinux/bios/*.c32 /boot/syslinux
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> If (/ and /boot on same fs):
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==>   # ln -s /usr/lib/syslinux/bios/*.c32 /boot/syslinux
[2013-10-22 15:56] [PACMAN] upgraded syslinux (4.07-1 -> 6.02-3)
[2013-10-22 15:56] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2013-10-22 15:56] [PACMAN] upgraded virtualbox-host-modules (4.2.18-7 -> 4.3.0-1)
[2013-10-22 15:56] [PACMAN] upgraded virtualbox (4.2.18-2 -> 4.3.0-1)

After merging in the changes from

/boot/syslinux/syslinux.cfg.pacnew

, I ran

/usr/bin/syslinux-install_update -i -a -m

, and then rebooted the system, and that's when I first discovered VirtualBox was no longer working.

I tried

sudo modprobe vboxdrv

,

sudo modprobe vboxnetadp

,

sudo modprobe vboxnetflt

and

sudo modprobe vobxpci

based on what I saw from https://bbs.archlinux.org/viewtopic.php?id=130317

I tried

chown root.root /tmp; chmod ug-s /tmp; chmod 1777 /tmp

based on what I saw from https://www.virtualbox.org/ticket/2335#comment:4

The output of

/bin/ls -ld /tmp

is

drwxrwxrwt 4 root root 80 Oct 22 16:46 /tmp

Not sure what to try next.

Last edited by Nebu (2013-10-22 21:33:35)

Nebu · 2013-10-22 21:43:52

For now, I've downgraded to my old version of VirtualBox by running

sudo pacman -U /var/cache/pacman/pkg/virtualbox-4.2.18-2-x86_64.pkg.tar.xz

until I can find a "real" fix for 4..3.0-1

Organ · 2013-10-23 20:58:22

Hi,

I've experienced the exact same issue.
I've spent all night trying to fix this, checking /tmp permissions, deleting ".vbox.*" files, and so on.
Downgrading solved the problem.

Last edited by Organ (2013-10-23 21:01:59)

barrakuda · 2013-10-24 02:46:24

Same from here. I updated to 4.3.0-2, but this issue still happened.

Currently downgrading to 4.2.18 is a feasible solution.

loxan · 2013-10-24 09:02:02

I also can confirm the same issue as with previous posters, tried all stuff found on the net that seems related to this issue.

Nothing so far as solved it for me, I also had to downgrade to 4.2.18. Not optimal but atleasat i can work until this has been sorted out.

Last edited by loxan (2013-10-24 09:02:19)

HalJ · 2013-10-24 18:45:29

I've got the same issue after upgrading to 4.3.0-2 today. I ran through the same troubleshooting steps as everyone else, but nothing worked. Time to downgrade.

attwo · 2013-10-24 20:12:16

I am having the same problem as everyone else, apparently, and I confirm that the "-2" upgrade does not help. Does anyone have a package of the latest working build? I accidentally cleared my pacman cache. Is recompiling the only option?

ddanier · 2013-10-24 20:47:04

Would like to get the 4.2.18er packages, too (i686). Manual rebuild failed. 4.3 is currently not useable for me.

Seems like none of the workarounds (like /tmp fixes) do not change anything.

Could provide x86_64 packages. (virtualbox-4.2.18-2-x86_64.pkg.tar.xz, virtualbox-host-modules-4.2.18-7-x86_64.pkg.tar.xz)

ddanier · 2013-10-25 08:37:21

I just switched over to virtualbox-bin (AUR), which solved to problem for now.

radionecrotic · 2013-10-29 06:08:02

Try installing the libvpx package. When I strace'd vboxmanage, it died trying to load libvpx.so.1.

radionecrotic · 2013-10-29 07:00:32

I filed a bug against the package.

mrmcan · 2013-10-29 22:36:49

+1 switched to virtualbox-bin from aur, and solved problem.

loxan · 2013-10-30 07:39:57

Yep, it was indeed missing the libvpx pkg, installing that solved it for me also.

sasa13e · 2015-08-21 08:21:14

radionecrotic wrote:

Try installing the libvpx package. When I strace'd vboxmanage, it died trying to load libvpx.so.1.

IT WORKS!!!!! (in 2015 too)

galago · 2015-11-13 14:03:53

sasa13e wrote:

radionecrotic wrote:
Try installing the libvpx package. When I strace'd vboxmanage, it died trying to load libvpx.so.1.
IT WORKS!!!!! (in 2015 too)

I encountered exactly the same error today ! Thanks to radionecrotic, I solved the problem.

VirtualBox - Critical Error
Failed to create the VirtualBoxClient COM object.
The application will now terminate.
Details:  
Callee RC: 
NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)

Environment:
4.2.5-1-ARCH x86_64
virtualbox 5.0.8-2 [Community][2015-11-11]

Solution:
1. Download libvpx-1.5.0-2-x86_64.pkg.tar.xz from https://www.archlinux.org/packages/extra/x86_64/libvpx/
2. Extract "libvpx.so.3.0.0" from libvpx-1.5.0-2-x86_64.pkg.tar.xz to /usr/lib/virtualbox/libvpx.so.3

Description:
When I run "#strace VBoxManage list groups", I found the following error messages:

open("/usr/lib/virtualbox/libvpx.so.3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/virtualbox/libvpx.so.3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/tls/x86_64/libvpx.so.3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/tls/x86_64", 0x7ffc89596e60) = -1 ENOENT (No such file or directory)
open("/usr/lib/tls/libvpx.so.3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/tls", 0x7ffc89596e60)    = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64/libvpx.so.3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64", 0x7ffc89596e60) = -1 ENOENT (No such file or directory)
open("/usr/lib/libvpx.so.3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

As suggested by radionecrotic, I tried to run "#pacman -S libvpx". However, it said:

error: failed to prepare transaction (could not satisfy dependencies)
:: ffmpeg: requires libvpx.so=2-64

So I had to move libvpx.so.3.0.0 to /usr/lib/virtualbox/libvpx.so.3.
This method is kind of dirty, but it do works.

Last edited by galago (2015-11-13 14:06:35)

loqs · 2015-11-13 16:04:37

galago wrote:

As suggested by radionecrotic, I tried to run "#pacman -S libvpx". However, it said:
error: failed to prepare transaction (could not satisfy dependencies)
:: ffmpeg: requires libvpx.so=2-64

ffmpeg currently requires libvpx.so=3-64 a full system upgrade should rectify the issue.
Partial_upgrades_are_unsupported

galago · 2015-11-14 08:27:16

loqs wrote:

galago wrote:
As suggested by radionecrotic, I tried to run "#pacman -S libvpx". However, it said:
error: failed to prepare transaction (could not satisfy dependencies)
:: ffmpeg: requires libvpx.so=2-64
ffmpeg currently requires libvpx.so=3-64 a full system upgrade should rectify the issue.
Partial_upgrades_are_unsupported

You are right! Now the conflict is gone after a full system upgrades.

grubenm · 2015-11-21 17:05:51

loqs wrote:

galago wrote:
As suggested by radionecrotic, I tried to run "#pacman -S libvpx". However, it said:
error: failed to prepare transaction (could not satisfy dependencies)
:: ffmpeg: requires libvpx.so=2-64
ffmpeg currently requires libvpx.so=3-64 a full system upgrade should rectify the issue.
Partial_upgrades_are_unsupported

I, too, received this error code, but simply issued

sudo pacman -S ffmpeg

and the newer libvpx package was pulled in.
After libvpx was upgraded, virtualbox started without error.
(was receiving NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)).

dquasar · 2016-10-11 16:54:37

Hello everyone!
I think this a really important result, could someone tell the maintainer to update the package and update the dependencies?

Thanks

Arch Linux

#1 2013-10-22 20:55:08

VBoxManage: error: Failed to create a session object!

#2 2013-10-22 21:43:52

Re: VBoxManage: error: Failed to create a session object!

#3 2013-10-23 20:58:22

Re: VBoxManage: error: Failed to create a session object!

#4 2013-10-24 02:46:24

Re: VBoxManage: error: Failed to create a session object!

#5 2013-10-24 09:02:02

Re: VBoxManage: error: Failed to create a session object!

#6 2013-10-24 18:45:29

Re: VBoxManage: error: Failed to create a session object!

#7 2013-10-24 20:12:16

Re: VBoxManage: error: Failed to create a session object!

#8 2013-10-24 20:47:04

Re: VBoxManage: error: Failed to create a session object!

#9 2013-10-25 08:37:21

Re: VBoxManage: error: Failed to create a session object!

#10 2013-10-29 06:08:02

Re: VBoxManage: error: Failed to create a session object!

#11 2013-10-29 07:00:32

Re: VBoxManage: error: Failed to create a session object!

#12 2013-10-29 22:36:49

Re: VBoxManage: error: Failed to create a session object!

#13 2013-10-30 07:39:57

Re: VBoxManage: error: Failed to create a session object!

#14 2015-08-21 08:21:14

Re: VBoxManage: error: Failed to create a session object!

#15 2015-11-13 14:03:53

Re: VBoxManage: error: Failed to create a session object!

#16 2015-11-13 16:04:37

Re: VBoxManage: error: Failed to create a session object!

#17 2015-11-14 08:27:16

Re: VBoxManage: error: Failed to create a session object!

#18 2015-11-21 17:05:51

Re: VBoxManage: error: Failed to create a session object!

#19 2016-10-11 16:54:37

Re: VBoxManage: error: Failed to create a session object!

Board footer