Callee RC: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)

[karimp]

My VB was working fine. I did forced shutdown so it got currepted, now I was not able to start it even.

So I used another system, copied to source files (images) from my actual and tried to load previous VM images. So when I try to open it, it gives

Failed to attach the hard disk (C:\Users\karimkhan.pathan\Downloads\UbuntuVM\Ubuntu-hdd.vdi) to the slot SATA Port 0 of the machine k.

Callee RC: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)

Okay, So location of my VB is C:\Users\karimkhan.pathan\VirtualBox VMs\Ubuntu\Snapshots\{a61ac67a-168b-48a9-beb0-2e0cc8b1f8ff}

But When I load it in my VB, it says C:\Users\karimkhan.pathan\Downloads\UbuntuVM\Ubuntu-hdd.vdi failed to attache. Why it is redirecting to different vdi?

C:\Users\karimkhan.pathan\Downloads\UbuntuVM\Ubuntu-hdd.vdi This file I am directly able to load in VB, but it is older image.

I think my latest image is in "C:\Users\karimkhan.pathan\VirtualBox VMs\Ubuntu\Snapshots\{a61ac67a-168b-48a9-beb0-2e0cc8b1f8ff}" Which I need to load.

I tried various solution but did not help.

"C:\Users\karimkhan.pathan\VirtualBox VMs" contains various folders. For each of them I tried soln given on various fourm, but no luck

C:\Users\karimkhan.pathan>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" st
artvm a --type emergencystop
VBoxManage.exe: error: The machine 'a' is not locked by a session
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), c
omponent MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "LaunchVMProcess(a->session, sessionType.raw(),
env.raw(), progress.asOutParam())" at line 589 of file VBoxManageMisc.cpp


C:\Users\karimkhan.pathan>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" st
artvm default --type emergencystop
VBoxManage.exe: error: Could not find a registered machine named 'default'
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), compo
nent VirtualBoxWrap, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: "FindMachine(Bstr(pszVM).raw(), machine.asOutPar
am())" at line 572 of file VBoxManageMisc.cpp

C:\Users\karimkhan.pathan>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" st
artvm Ubuntu --type emergencystop
VBoxManage.exe: error: Could not find a registered machine named 'Ubuntu'
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), compo
nent VirtualBoxWrap, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: "FindMachine(Bstr(pszVM).raw(), machine.asOutPar
am())" at line 572 of file VBoxManageMisc.cpp

Any help to recover it highly appreciate.

[scottgus1]

I did forced shutdown

I will assume this is the host PC you forced to shut down, since a forced guest shutdown will not likely prevent Virtualbox from restarting the guest.

Be sure you copied the "source files" to your new host PC correctly. See Moving a VM.

If you have let Virtualbox decide where to put the guest's files, you will have one folder containing all the guest files inside. You will move the whole guest folder, and all the files within, to the new host. When you get the guest folder moved to the new host you can double-click the guest's .vbox file to register the guest in the last state it was in when your old host PC started to have trouble.

On your new host you may need to clear out the guest setup you have been trying already. If your new host PC did not have any Virtualbox guests on it, the easiest way to clear out the previous attempt from Virtualbox would be to reboot the host PC, then move the folder "C:\Users\{yourusername}\.Virtualbox" folder to another place on your C drive. (Move not Copy, the .Virtualbox folder needs to be gone from C:\Users\{yourusername}.) Then restart Virtualbox. The main Virtualbox window will be empty and you can double-click the guest's .vbox file to register the copied guest.

If you did have other guests on the new Host PC, instead of moving the .Virtualbox folder, you will have to remove the copied guest from the main list and any references to the guest's virtual drive files from the Virtual Media Manager in the File menu.