After successful ride on VirtualBox 3.2 stable version, today I had a issue with starting my virtual machines. The following message appeared, The VM session was closed before any attempt to power it on, then closed. Finally I managed to fix with following method. Now VMs are fine.
I tried following methods, but failed.
1) Tried several snapshots which gave me same error.
2) Restarted Host computer.
3) Stopped all VirtualBox services and restarted.
All failed, finally Google helped me to find out this thread in VirtualBox.
If you get The VM session was closed before any attempt to power it on message and Virtual Machines can not be started, don’t panic. Don’t do anything. Just take a snapshot.
Go to Storage option of VM; remove hard disks and CD drives.
Start Virtual machine now. At least now you could see Oracle VirtualBox screen but as expected boot medium error you will get. Shut down VM and add storage disks as it was earlier.
Now switch on virtual machine, which will start normally.
I didn’t try much to find out the cause. VirtualBox may come up with some fixes for this issue. But, I can confirm this method work for me.
Is this fixed your issue too?
Hi, Thanks for this. It fixed the issue
cheers,
benjy
Hi,
thanks, it worked for me too.
@Maxi,
Thanks for informing.
Thanks so much, worked for me in a time of need!
Solved my problem – thank you!
Thank you! Your suggestion also fixed the same error on my 3.2.8 VirtualBox.
@Aia, it means 3.2.8 also having same issue? very sad.
Anyhow, Thanks for your comment.
Had the same error after upgrading. CD was still pointing to the Virtual Box Guest Additions CD (from the previous version). I changed it to empty and it booted. So little bit faster than removing and re-adding all the drives – maybe it will work for you!
Works for me
Thanks!
(VBox 3.2)
Had the same problem and followed what Nick suggested regarding the CD pointing to the additions. Fixed my issue.
@Jester,
Thanks for confirming this method too.
Just got the same error after installing the VmServiceControl.
I got it working again with :
VmServiceControl.exe -k
That kills the process.
@Guillaume B,
Thanks for one more fix.
Thanks so much. This fixed for me!
This blogpost saved my ass. thanks!
Close virtual box; go to the directory where virtualbox is installed
Run: VBoxManage discardstate
see http://www.virtualbox.org/manual/ch08.html for details
Thanks – worked for me. Starting to pull my hair out with V’Box….
Cheers,
Crispin
Hi there, I clicked change and then changed the sort order of the boot-steps and have set the HD first. Then it worked as well.
Thanks!
Fixed the issue for me. Cheers!
It did not fix ANYTHING!!!!! I removed ALL storage devices in the VM, tried to boot, and I got the message again. The only workaround is to create a NEW VM and reinstall everything! What is the point of giving false information? This is getting me extremely MAD! I cannot rely on anything on the Internet, because EVERYTHING is FALSE and OUTDATED!!!! Before I got stuck with this, the VM was extremely slow. I took ages just to install something in the virtual Ubuntu, which was periodically hanging. I know that Ubuntu itself is a possible cause for the problem, but now, that is VirtualBox that refuses to start the VM with my Ubuntu, so I would have to restart the installation again. It’s been almost TWO HOURS I am trying to install the Ubuntu guest, and now I would have to start again.
What can I do to install a virtual machine if VirtualBox does NOT work at ALL?
/Rant
thanx!
you saved my life!
Hi, I encountered the same error. I tried the solution but the error still comes up.
Just rebooting the host PC, starting VB solved the problem…
Mine fixed too, strange issue.
Thanks a lot, you saved me!
thanks, it worked!
It worked. Thanks!
Thanks for the tip. What worked for me and is worth trying first, if you have a saved machine state, is just discarding it — Machine – Discard.
amazing post dude !!!:)
Thanks, this really helped me out!