Error: Failed to open a session for the virtual machine - session was closed before any attempt to power it on

[Leigh Wardle]

I upgraded VirtualBox to version 3.2.2-62321 on a Windows 7 Ultimate 64-bit host. Everything was working fine with the previous version 3.1.8.

Since the upgrade to Virtualbox to version 3.2.2-62321, when I start any of my virtual machines I get the following error:

Failed to open a session for the virtual machine MyMachineName.

The VM session was closed before any attempt to power it on.

Details:

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

At the time of the upgrade, 11 guests were in a saved state and not powered off, 1 guest was powered off.

Attempting to start any of the guests gives the error and in no case does a log get created.

I have since installed VirtualBox 3.2.4, but that made no difference.

I posted the issue on the Forums: ​http://forums.virtualbox.org/viewtopic.php?f=6&t=31778&start=0

Regards, Leigh

[roberto de renzi]

Replying to leigh_wardle:

I upgraded VirtualBox to version 3.2.2-62321 on a Windows 7 Ultimate 64-bit host. Everything was working fine with the previous version 3.1.8.

Since the upgrade to Virtualbox to version 3.2.2-62321, when I start any of my virtual machines I get the following error:

Failed to open a session for the virtual machine MyMachineName.

The VM session was closed before any attempt to power it on.

Happens also with 3.2.4-624

Details:

Result Code: E_FAIL (0x80004005) Component: Machine Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

At the time of the upgrade, 11 guests were in a saved state and not powered off, 1 guest was powered off.

Attempting to start any of the guests gives the error and in no case does a log get created.

I have since installed VirtualBox 3.2.4, but that made no difference.

I posted the issue on the Forums: ​http://forums.virtualbox.org/viewtopic.php?f=6&t=31778&start=0

Regards, Leigh

[Eugeni Dodonov]

I am facing the same issue. Any known workaround or solution?

[Leigh Wardle]

The workaround is to re-install an earlier version - VirtualBox 3.1.8 now works for me. Let me know if you want a copy....

[Frank Mehnert]

Well, if really no VBox.log file is created it would be still interesting to see at least one VM configuration here. So it would be appreciated if you could attach one XML file of such a VM which fails to start.

[Leigh Wardle]

Sample XML file of a VM that fails to start (note:none of my VMs will start)