VirtualBox

Opened 3 years ago

Closed 3 years ago

#20679 closed defect (fixed)

VirtualBox should not wipe saved state after it fails to restore => fixed in svn/6.1.x x>26

Reported by: szx Owned by:
Component: other Version: VirtualBox 6.1.26
Keywords: Cc:
Guest type: other Host type: other

Description

I tried to restore a VM from a saved state and there was an error. Now the saved state is lost and the VM is "Aborted".

In such situations, I think it's reasonable to keep the saved state info/snapshot so that the user can try restoring again later, instead of deleting it.

Change History (1)

comment:1 by BP, 3 years ago

Resolution: fixed
Status: newclosed
Summary: VirtualBox should not wipe saved state after it fails to restoreVirtualBox should not wipe saved state after it fails to restore => fixed in svn/6.1.x x>26

We agree that it is reasonable to keep the saved state if the VM fails to boot from the "Saved" state so this was fixed in VirtualBox 6.1.28 which was released on October 19th, 2021. The change in 6.1.28 and later maintains the VM's "Saved" state if it fails to restore the saved state file. In the development branch of VirtualBox a new Machine state was added called "Aborted-Saved" which similarly preserves the saved state file if the VM fails to powerUp()/restore from the "Saved" state.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy