Opened 10 years ago
Closed 10 years ago
#12397 closed defect (fixed)
vboxmanage startvm crashes after restorestate
| Reported by: | Jaymzu | Owned by: | |
|---|---|---|---|
| Component: | guest control | Version: | VirtualBox 4.3.2 |
| Keywords: | startvm crash | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
After powering off a machine and doing restorestate, vboxmanage startvm fails. When trying the same command again it works.
When doing just poweroff and startvm (without restorestate) it works just fine.
root@Darkside:~/cuckoo/utils# VBoxManage controlvm cuckoo1 poweroff 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% root@Darkside:~/cuckoo/utils# VBoxManage snapshot cuckoo1 restorecurrent Restoring snapshot a402eb58-481f-4ace-b17e-4409101436c3 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% root@Darkside:~/cuckoo/utils# VBoxManage startvm cuckoo1 Waiting for VM "cuckoo1" to power on... VBoxManage: error: No error info VBoxManage: error: Details: code NS_ERROR_CALL_FAILED (0x800706be), component ProgressProxy, interface IProgress root@Darkside:~/cuckoo/utils# VBoxManage startvm cuckoo1 Waiting for VM "cuckoo1" to power on... VM "cuckoo1" has been successfully started.
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Please attach a VBox.log file for the VM session where you try to start the VM from the saved state.
comment:3 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Still no VBox.log file. Please reopen if still relevant with VBox 4.3.6 and attach a corresponding VBox.log file in that case.
apologies for the bad formatting. Should have used the preview button ;(