VirtualBox

Ticket #6930 (new defect)

Opened 5 years ago

Last modified 42 hours ago

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

Reported by: leigh_wardle Owned by:
Priority: major Component: other
Version: VirtualBox 3.2.4 Keywords:
Cc: Guest type: other
Host type: other

Description (last modified by frank) (diff)

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

Attachments

Potoroo 2010-05-30.xml Download (9.6 KB) - added by leigh_wardle 5 years ago.
Sample XML file of a VM that fails to start (note:none of my VMs will start)

Change History

comment:1 in reply to: ↑ description Changed 5 years ago by derenzi

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

comment:2 Changed 5 years ago by eugeni

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

comment:3 Changed 5 years ago by 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....

comment:4 Changed 5 years ago by frank

  • Description modified (diff)

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.

Changed 5 years ago by leigh_wardle

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

comment:5 Changed 5 years ago by leigh_wardle

Frank - I have attached a Sample XML file of a VM that fails to start (note:none of my VMs will start). Leigh

comment:6 Changed 5 years ago by jong_2000

I am experiencing the same problem. Any update or workaround?

comment:7 Changed 5 years ago by 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....

comment:8 Changed 5 years ago by jong_2000

Thanks. Reinstalling 3.1.8 worked. It can be downloaded from  http://www.virtualbox.org/wiki/Download_Old_Builds_3_1.

comment:9 follow-up: ↓ 15 Changed 5 years ago by ulogic

The bug also exists in 3.2.6. What has corrected the problem for me is to release the VBoxGuestAdditions.iso from the CD/DVD device. I have also noticed that I have two of them in the virtual media manager. My installation is in C:\Apps\VirtualBox. The two devices' locations are listed as C:\Apps\VIRTUAL~1\VBoxGuestAdditions.iso (which is the one currently selected) and C:\Apps\VirtualBox\VBoxGuestAdditions.iso Switching to the other device also seems to fix the problem. After switching back to the original one, the virtual machine will still start up again. Go figure!

comment:10 Changed 5 years ago by whistman

I have the same error, after upgrading to Windows 7 Ultimate x64 today. My Fedora 10 image will boot, but not my WinXP Pro VM. I did try to "show log" to post here, but making that selection results in VirtualBox "(Not Responding)". I'm running version 3.2.6 r63112.

comment:11 Changed 5 years ago by jong_2000

Just as an update, I still cannot get 3.2.6 to load my Windows XP VM on Windows 7, but I was able to get it to load on a machine running Vista SP2.

comment:12 Changed 5 years ago by foxyshadis

Still happens on 3.2.8. I needed to reboot the host, so I saved the state of the machine to hibernate, and after reboot, I get this exact error message and behavior, no logs generated. I discarded the state and attempted to start clean, but there was no change. My vCD drive had nothing in it, but when I removed the CD entirely and I could finally successfully start the VM.

comment:13 Changed 2 years ago by vboxer12

I had this same error message and similar symptom yesterday.

After a hurried close-down of the vm before the client system is boot up. I quickly reverted the vm to a child snapshot of a bunch of 2nd level snapshots,

Then I cant start that vm anymore, reverting to any other snapshot won't help either. No log is generated in Log folder, which means the logger hasn't even start when the error occurs.I tired to change various virtual network settings. I evening manually edited the .vbox file, replaced the top level "Hardware" node with that of the snapshot I am currently using. No use.

After a couple of failed attempts to start the VM. I opened process explorer. And viola, so many hanged vitrualbox process idling there. After killing them all, including the COM server. My vm is back to life.

Hope this helps.

comment:14 Changed 2 years ago by lhilden

This bug still exists on 4.2.16 r86992 OSX Host, Windows 7 client. I rebooted the host and the issue cleared up.

comment:15 in reply to: ↑ 9 Changed 20 months ago by Bhaspro

Thanks. After releasing VBoxGuestAdditions.iso from the CD/DVD device. It worked fine.

Replying to ulogic:

The bug also exists in 3.2.6. What has corrected the problem for me is to release the VBoxGuestAdditions.iso from the CD/DVD device. I have also noticed that I have two of them in the virtual media manager. My installation is in C:\Apps\VirtualBox. The two devices' locations are listed as C:\Apps\VIRTUAL~1\VBoxGuestAdditions.iso (which is the one currently selected) and C:\Apps\VirtualBox\VBoxGuestAdditions.iso Switching to the other device also seems to fix the problem. After switching back to the original one, the virtual machine will still start up again. Go figure!

comment:16 Changed 9 months ago by Karel Doorman

Had same problem. But was due to already open (ghost) Virtual Box session which i only could detect in the Task Manager. Killed that process. Start Virtual Box and instance again. problem solved. Windows 8. VB version 4.3.18.

comment:17 Changed 8 months ago by ramprasad

I also got same error as 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}

workaround done and it worked me Some windows patches are installed as part of patch update by our admin team. I have removed/uninstalled the patches. intsalled virtual box again.

It worlked for me.

comment:18 Changed 7 months ago by bhatmann

I updated to VirtualBox 4.3.20 on a host Windows 7 64-bit machine and my Ubuntu 14.04 guest vmdk wouldn't start due to the above issue.

A simple restart of the host fixed the issue for me.

Last edited 7 months ago by bhatmann (previous) (diff)

comment:19 Changed 6 months ago by esitoris

I do have the same error as well (Failed to open a session for the virtual machine MyMachineName).

The details show:

Result Code: E_FAIL (0x80004005) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

During teh days before this error, I have niticed that:

After starting my laptop again (that was set on Hibrenate), I di see that the VM was closed on its own. At starting it again -> I do get the warning tha it was abnormally closed, with the choice of the way of starting it again. I did choose "Normal".

However, today I do not get father than the above error when trying to "Start".

So in that way I cannot get to my applications and data :(

I would be very thankful for any helo/suggestion!

Thanks,

Elvis

comment:20 follow-up: ↓ 21 Changed 6 months ago by hpmz

I have got this error as well : [Failed to open a session for the virtual machine MyMachineName. The VM session was closed before any attempt to power it on]

And my vm was in saved state. Tried to restart the host, didnt help. Then I tried to discard from its saved state. So right clicked on the VM and selected "Discard Saved State". This resolved the issue and I was able to start my VM back.

comment:21 in reply to: ↑ 20 Changed 3 months ago by Ugo

Replying to hpmz:

I have got this error as well : [Failed to open a session for the virtual machine MyMachineName. The VM session was closed before any attempt to power it on]

And my vm was in saved state. Tried to restart the host, didnt help. Then I tried to discard from its saved state. So right clicked on the VM and selected "Discard Saved State". This resolved the issue and I was able to start my VM back.

I did the same and it worked for me.

comment:22 Changed 3 months ago by FractalizeR

Found some orphaned VirtualBox process, consuming about 50Mb RAM and some CPU, killed it. VM started ok.

comment:23 Changed 4 weeks ago by jmer1234

* FIXED * I ran in to this issue with version 4.3.28 on Windows 7. The virtual disk and machine files are installed in a folder in the Program Files (x86) folder. At some point after installation, and while the VM has been running, the user I was logged into the Windows 7 machine as lost write permissions to this folder/set of files. The permission issue did not affect me until I tried to restart the VM. After granting the user write permissions to the parent folder, the VM started normally.

Last edited 4 weeks ago by jmer1234 (previous) (diff)

comment:24 Changed 42 hours ago by maciej.kowalski

Hi everyone. I had the same problem recently. After I installed the new version of VirtualBox (5). I resolved it in the following way:

Settings/Storage/Storage Tree/Optical Drive (Empty) - left click/Attributes/Optical Drive - left click on the disc icon/Choose Optical Virtual Disc File/Choose System ISO (Live or Not)

I clicked on "OK" button. Then I clicked on the "Start" button.

Now everything works fine (On my PC).

This applies to the following error (Choose an image to run window - not session was closed):

Failed to open a session for the virtual machine Slax. The VM session was aborted,

Result Code: E_FAIL (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

Last edited 42 hours ago by maciej.kowalski (previous) (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use