Backlog #3085
snapshots, persistent across reboots, migrations, and shutdowns
| Status: | Closed | Start date: | 07/22/2014 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Drivers - VM | |||
| Target version: | - |
Description
Snapshots created from VM menu, snapshot tab should be persistent across VM migrations, stops or reboots. Imagine situation that snapshot is made for a quick rollback while I deploy some new features to application. Now when the machine is stoppped or migrated in case of some problem I will lose possibility to rollback.
Related issues
History
#1
Updated by Ruben S. Montero almost 7 years ago
- Tracker changed from Feature to Backlog
- Category set to Drivers - VM
- Priority changed from Normal to High
Some versions of libvirt/qemu do not support this feature, it seems that current one may have address this. I'll keep this open to further investigate this and update the core behavior if needed.
Cheers
#2
Updated by EOLE Team over 6 years ago
+1
We heavily use snapshots during development and testing, as the infrastructure admin, I sometime want to suspend users VMs to operate on a node, but as snapshots are delete I can't.
Regards.
#3
Updated by Carlos Martín about 6 years ago
- Related to Bug #3740: VM snapshots not visible after powercycle (poweroff / resume) added
#4
Updated by Carlos Martín about 6 years ago
- Related to Backlog #3187: Persistent VM snapshots added
#5
Updated by Ruben S. Montero about 5 years ago
- Status changed from Pending to Closed
Closing this as #3187 duplicates it. Keeping that one open, as it has more feedback