VirtualBox 5.0.4 Failed to open a session

[Sanso13527]

Failed to open a session for the virtual machine
details
The virtual machine '10' has terminated unexpectedly during startup with exit code 1 (0x1).
More details may be available in 'C:\Users\Sanso\VirtualBox VMs\10\Logs\VBoxStartup.log'.


Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

can anyone could you please help me to solve this problem ?

[socratis]

More details may be available in 'C:\Users\Sanso\VirtualBox VMs\10\Logs\VBoxStartup.log'.

The error message told you exactly what to look for. ZIP the above mentioned log and attach it here.

[Linus234]

HI,

I get the same error with VB 5.0.4 on Windows 7.
My log file is attached.

Help would be greatly appreciated.

[JohnPruitt33]

I do have the exact same problem as poster above "Linus234 ".

I would like to add this piece of information:
after installing, I click "restart", and then, in the moment that windows is shutting down, I can see for a tiny moment a window from virtual box, and I can read "installation failed"; but I can´t read the whole information as the system shutdown continues. I can´t interrupt the shutdown process, I can´t make a screenshot of the info-window.
I can´t find the information of that window in the log files.

Also, I tried with the previous release "VirtualBox-4.3.30-101610-Win", it gave me the same problems, not able to start a newly created box.

I use Lenovo Thinkpad.
I can provide more details but maybe there are already solutions?

[code]

Same problem here. Must be a recent update because it was working 2 days ago.

I'm running Ubuntu 14.04 and VirtualBox 5.0.4-102546~Ubuntu.

It segfaults when trying to start any VM. The VirtualBox log file isn't that helpful. apport says "VirtualBox crashed with SIGSEGV in QWidgetItemV2::updateCacheIfNecessary()" but the stack trace goes a few calls deeper than that into VirtualBox.so

I don't see anything obvious in my update history. The kernel and nVidia driver were updated yesterday. You guys also running nVidia?

[Linus234]

You guys also running nVidia?

No, my laptop (Windows 7) has an Intel Graphics Card.

[Linus234]

Same problem here. Must be a recent update because it was working 2 days ago.

I'm running Ubuntu 14.04 and VirtualBox 5.0.4-102546~Ubuntu.

It segfaults when trying to start any VM. The VirtualBox log file isn't that helpful. apport says "VirtualBox crashed with SIGSEGV in QWidgetItemV2::updateCacheIfNecessary()" but the stack trace goes a few calls deeper than that into VirtualBox.so

Just to make sure that we are really talking about the same kind of error here: Do you also get

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Or what makes you think, you are facing the same issue?

[code]

Just to make sure that we are really talking about the same kind of error here: Do you also get

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Or what makes you think, you are facing the same issue?

Yes, exactly the same.

I missed where you posted your log file. I'll compare mine. It could very well be a different issue producing the same error code, I'm not sure.

[frank]

Same problem here. Must be a recent update because it was working 2 days ago.

I'm running Ubuntu 14.04 and VirtualBox 5.0.4-102546~Ubuntu.

It segfaults when trying to start any VM. The VirtualBox log file isn't that helpful. apport says "VirtualBox crashed with SIGSEGV in QWidgetItemV2::updateCacheIfNecessary()" but the stack trace goes a few calls deeper than that into VirtualBox.so

Just to make sure that we are really talking about the same kind of error here: Do you also get

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Or what makes you think, you are facing the same issue?

Guys, if this is Linux and you get this problem with VBox 5.0.4 then it's most likely that the VirtualBox host kernel modules (vboxdrv, vboxnetflt, vboxnetadp and vboxpci) are not loaded. There is a bug in 5.0.4 which makes the GUI crash in that case. Just make sure the kernel modules are installed by doing

Code: Select all

/etc/init.d/vboxdrv setup

. The bug will be fixed with the next maintenance release. If you use DKMS (available on Ubuntu), this will take care that the VirtualBox kernel modules are automatically re-compiled if you upgrade your host kernel.

[code]

Guys, if this is Linux and you get this problem with VBox 5.0.4 then it's most likely that the VirtualBox host kernel modules (vboxdrv, vboxnetflt, vboxnetadp and vboxpci) are not loaded. There is a bug in 5.0.4 which makes the GUI crash in that case. Just make sure the kernel modules are installed by doing

Code: Select all

/etc/init.d/vboxdrv setup

. The bug will be fixed with the next maintenance release. If you use DKMS (available on Ubuntu), this will take care that the VirtualBox kernel modules are automatically re-compiled if you upgrade your host kernel.

Worked, thanks! Sorry for the noise. My issue is probably not what the OP is experiencing.

[Linus234]

Sorry for the noise. My issue is probably not what the OP is experiencing.

No worries!

But I would never the less still be interested in a solution for my error occuring in windows.

Can anyone make sense of the log I uploaded?

[stamish]

To Frank Mehnert. I was having the problems expressed in this post! Your answer to recompile VB was awesome! I can't prove it but I believe I created a conflict by loading XP, Centos and openSUSE in as 32 bit and then Windows 7 as 64 bit! Everything worked fine for a while then nothing would open. After recompiling the VB Windows 7 gave a 64 bit error so I'm going to load up a different Virtual Box to use Windows 7 on. Again, thanks for the answer.