[Solved] Failed to open session...

[52ROSt]

I created a Windows 7 VM with only W7 installed.

When start this engine I get the error message:

Failed to open a session for the virtual machine ... machine name...

Locking of attached media failed. A possible reason is that one of the media is attached to a running VM.

Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)
Component: SessionMachine

Other VMs start.

Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

What is causing the problem and how can I solve it?

Thanks in advance for your help!

[BillG]

So it says that the file is attached to another vm but you don't have any other vms? Is that it?

What can you see in the Virtual Media Manager apart from the .vdi for this vm?

[52ROSt]

...that the file is attached to another vm...

I created this VM from scratch and exported it for backup reasons.

I attached a screen shot of the settings.

If you need more information, please let me know.

[52ROSt]

As other might run into the same problem, here is what I did.

Just created a new machine because the original one had only W7 installed nothing else.
At the end of the installation I recognized, that I most properly did not remove the installation DVD when shutting down the machine. This could be the "media" mentioned in the error message.

I did several shut down and start up procedures and the VM works fine.

I keep this thread unsolved for a few days to allow some experts (e.g. Bill) to give a better advice. I am a newbie.

[Carl.Li]

I met this issue too. I tried to export a VM but force quitted before it's finished. Then I can't start that VM, it showed the same error with you.

What did I do to fix this issue?
1. Quit virtual box
2. End all virtualbox related processes.
3. Now I can start that VM again

[socratis]

2. End all virtualbox related processes.

That's what most probably fixed it, a stuck VBoxSVC process. BTW, this process (VBoxSVC), along with the VBoxNAT and VBoxNetDHCP processes, can take up to a minute to terminate after every VM has stopped. So, just for future reference, you should give it some time before "killing" it.