27
votes

I have a virtual machine with Windows XP with a clean installation. I set it as immutable to create a differential machine, so I create a new virtual machine, select the immutable hard disk and create a new snapshot in the new virtual machine folder.

However, when I try to start the virtual machine I get this error:

"failed to open a session for the virtual machine".

Código Resultado: 
VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)
Componente: 
ProgressProxy
Interfaz: 
IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

What is the problem? until now I can use differential virtual machines without problems. I have installed the last version or VirtualBox v4.3.4 and the problem persists.

If I set the hard driver as normal and I create a new virtual machine and select this hard drive I don't have any problem.

EDIT: I use the same virtual disk and do the same steps in another computer and it works fine. I think that the problem is the VirtualBox of my computer with the problem, but I try to uninstall the program and reinstall it and the problem persists, so I don't know how to solve the problem.

EDIT 2: if I set the virtual harddrive as multiattached instead of immutable, then it works fine. In my case is enough, but I know that it would be work as immutable because it was work until now and it works in another computer.

I try to create a new user in windows to try if the problem if with the configuration of my account, but the problem persists. So I think that some general configuration of VirtualBox has been corrupted and I am not be able to repair it.

I would like to know if there is any solution to use a immutable hard drive, because I would like to solve the problem with VirtualBox, although by the moment the multiattached hard disk is enough.

13
I'm experiencing a similar problem when restoring a saved machine. I wonder if your issue and mine might be the same as this bug. It is probably a good idea to search through other VB bug tickets to see if there is a better match (my problem, and that ticket, is about restoring a saved machine, not starting a new one).halfer
Whilst this is a good question, I am going to see if it can be moved to SuperUser - this site is for programming questions. Thanks.halfer
I asked a mod for this to be moved, but it was declined as it is too old. You may get answers here, but please ask future questions of this kind on the correct site. Thanks!halfer

13 Answers

20
votes

I had the same issue, I tried editing the VM but it wasn't letting me save it. So I tried the following:

  1. Tried editing the VM to change RAM/CPU etc, but it wasn't letting me save it
  2. Deleted the vm (not the data) and tried adding it again, didn't fix it
  3. Tried moving the vbox file to another directory and import it, but it didn't let me move the vbox file so I realized there's a virtualbox process running that's holding a lock on it. So I killed that process and started it again and my VM booted
10
votes

Killing VM process dint work in my case.

Right click on the VM and click on "Discard Saved State".

 Right click on the VM and click on "Discard Saved State".

This worked for me.

7
votes

For windows users ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

I had the same issue, and this trick works for me

  1. Goto control panel
  2. Open Uninstall program
  3. Click on turn windows features on or off
  4. Scroll down and find the hyper-V folder.
  5. Uncheck the Hyper-V.
  6. Apply changes and restart your system.
  7. Now here you go... Open your virtual box and start the os you want.

Hope this helps..

5
votes

Updating VirtualBox to newest version fixed my issue.

1
votes

maybe it is caused by privilege, please try this:

#sudo chmod 755 /Applications 
#sudo chmod 755 /Applications/Virtualbox.app
1
votes

Something that I tried and work for me is simply you create a new virtual machine and you use the existing virtual hard disk file and everything is like you left it.

1
votes

If you are in Windows and the error message shows VT-x is not available make sure Hyper-V is disabled in Windows components.

1
votes

On Ubuntu, this can also be caused by incorrect permissions. I chmod 755 Logs/ which fixed the issue.

0
votes

For MAC users

After some research, this worked for me:

  • Quit VirtualBox
  • Right click "Applications" folder
  • Click on "Get Info"
  • Change "Everyone" Permission to "Read Only"
  • Open VirtualBox, and now it should work.

0
votes

Normally this error occurs when it try to load the previous state. This happened in Mac Virtual box. I tried after restarting the virtual box but again also i've encountered this issue. Right Click on the operating system in the virtual box and then Click on the Discard Saved State.. .This fixed the issue.

0
votes

try this

sudo update-secureboot-policy --enroll-key

and restart your system, when restart it shows option and select Mok key and you will work fine.

0
votes

The only thing that solved the issue for me is to unmount the second hard disk on my laptop. My current setup contains 1 HDD on SATA0 port and 1 SSD on SATA1 port. I've the OS and Oracle VirtualBox installed on the SSD drive. When I deleted the partition on the HDD, the issue was solved.

0
votes

In my case I gave administrator privilege to Virtualbox and it solved my problem. i.e., run run as administrator on windows 10