VirtualBox

Opened 8 years ago

Last modified 7 years ago

#16007 new enhancement

Allow overriding existing snapshots

Reported by: Tobbi Owned by:
Component: GUI Version: VirtualBox 5.1.6
Keywords: Cc:
Guest type: other Host type: other

Description

Currently, you can only specify a new snapshot from the Virtual Box VM menu. I think it would make sense if a window opens where you can select to override a snapshot, delete snapshots or create new ones.

Change History (4)

comment:1 by Socratis, 8 years ago

Like if you select a VM and look at the top-right corner where it says "Details | Snapshots"?

Take a look at the User Manual, Chapter 1.10.1 "Taking, restoring and deleting snapshots".

comment:2 by Tobbi, 7 years ago

The problem isn't actually restoring or deleting them. I'd much rather like to have an option to override an existing snapshot from the VM's menu.

comment:3 by Frank Mehnert, 7 years ago

I'm not sure if I understand your intention. Replacing a snapshot older than the latest created snapshot (e.g. snapshot '5') would only make sense if you go back to that snapshot (restore '5'), then run the VM and then create a new snapshot (e.g. snapshot '5a') plus discard the previous snapshot (discard '5'). A "Replace snapshot" operation would probably combine creating of the new snapshot and discarding of the other snapshot. A "replace snapshot" operation from the GUI would only make sense when applied to the latest snapshot. Your intention of such an operation is probably to have a convenient function which creates a snapshot of the most recent "working state", for example for backup reasons, without creating too many snapshots. Nevertheless such an operation would always first create a new snapshot and later discard the most recent snapshot.

But I think such a scenario (having one up-to-date snapshot of the know-to-be-working VM state) could make some sense.

comment:4 by Socratis, 7 years ago

Actually that's my modus operandi for all my VMs, so yeah, that idea I could support. I have one snapshot only per VM, to which I revert almost always. If I want a change permanently applied, I make the changes, take a second snapshot and delete the first.

Yes, it would make a lot of sense, but I'll leave it to the devs to figure out how many cans of worms it could open. Not in terms of implementation but of user-confusion.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use