(Nein, ich nutze Snapshots nicht als Pseudo-Backups, sondern ich "merke" mir damit verschiedene Installationszustände des Systems.)
Meine VM hat verschiedene Snapshots:
Code: Select all
$ vboxmanage snapshot w11-64i list
Name: Updates [2021-42] (UUID: 3521ae0b-d13b-4327-9dc2-19505e5cf22b)
Name: XXXX (UUID: 7a7da4b8-7a02-4ae3-a8d6-62fad385366d)
Name: Updates [2021-47] (UUID: 5edba047-d8b3-4f84-bf10-554788e0a6a2)
Name: [2021-12-04] (UUID: 885c0c79-d735-4781-939d-37cda0f43563)
Name: YYYY (UUID: e8e20277-1021-4b4e-8d19-5a65ae7cb591) *
Name: ZZZZ (UUID: 49160d85-e4f0-495b-808f-4168de2a83df)
Name: AAAA (UUID: ead2abf9-48a7-4f6d-9b93-4441b3807006)
Name: Base [2227] (UUID: 5c03c817-e7f1-4d22-8114-bfc4762195e8)
Code: Select all
$ vboxmanage snapshot w11-64i delete 885c0c79-d735-4781-939d-37cda0f43563
Deleting snapshot '[2021-12-04]' (885c0c79-d735-4781-939d-37cda0f43563)
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Snapshot operation failed
VBoxManage: error: Cannot lock hard disk '/VMs/1820/w11-64i/Snapshots/{ac696bd5-02e1-4d32-bce4-17a22b7dee5d}.vdi' when deleting a snapshot
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface IMachine
VBoxManage: error: --------
VBoxManage: error: Could not open the medium '/VMs/1820/w11-64i/Snapshots/{ac696bd5-02e1-4d32-bce4-17a22b7dee5d}.vdi'.
VBoxManage: error: VD: error VERR_FILE_NOT_FOUND opening image file '/VMs/1820/w11-64i/Snapshots/{ac696bd5-02e1-4d32-bce4-17a22b7dee5d}.vdi' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleSnapshot(HandlerArg*)" at line 552 of file VBoxManageSnapshot.cpp
Code: Select all
$ vboxmanage snapshot w11-64i restore 5edba047-d8b3-4f84-bf10-554788e0a6a2
Restoring snapshot 'Updates [2021-47]' (5edba047-d8b3-4f84-bf10-554788e0a6a2)
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
$ vboxmanage startvm w11-64i --type headless
Waiting for VM "w11-64i" to power on...
VM "w11-64i" has been successfully started.
Code: Select all
$ vboxmanage snapshot w11-64i restore e8e20277-1021-4b4e-8d19-5a65ae7cb591
Restoring snapshot 'YYYY' (e8e20277-1021-4b4e-8d19-5a65ae7cb591)
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
$ vboxmanage startvm w11-64i --type headless
Waiting for VM "w11-64i" to power on...
VM "w11-64i" has been successfully started.
Code: Select all
UUID: ac696bd5-02e1-4d32-bce4-17a22b7dee5d
Parent UUID: a3c28992-5300-4231-b42e-30095797b3fc
State: inaccessible
Type: normal (differencing)
Location: /VMs/1820/w11-64i/Snapshots/{ac696bd5-02e1-4d32-bce4-17a22b7dee5d}.vdi
Storage format: VDI
Capacity: 0 MBytes
Encryption: disabled
Da er das Ende einer Kette ist, brauche ich ihn nicht, es entsteht also kein Datenverlust.