[v2] Mark and document restore with managed save as risky

[libvirt] [PATCH v2 0/3] Mark and document restore with managed save as risky

Michael Weiser posted 3 patches 4 years, 3 months ago

Diff against v3
Download series mbox

Test syntax-check failed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/20200102160026.2997988-1-michael.weiser@gmx.de

There is a newer version of this series

docs/manpages/virsh.rst | 39 ++++++++++++++++++++++++---------------
src/qemu/qemu_driver.c  |  9 +++++++++
2 files changed, 33 insertions(+), 15 deletions(-)

Expand all Fold all

[libvirt] [PATCH v2 0/3] Mark and document restore with managed save as risky

Posted by Michael Weiser 4 years, 3 months ago

This series marks restore of an inactive qemu snapshot while there is
managed saved state as risky due to the reasons explained in patch 1 and
3. Patch 2 is a simple reformatting of the documentation with no other
changes in preparation of addition of more reasons why reverts might
need to be forced.

Changes from v1:
- reword error message to "error: revert requires force: snapshot
  without memory state, removal of existing managed saved state strongly
  recommended to avoid corruption"
- add documentation of the new behaviour

Michael Weiser (3):
  qemu: Warn of restore with managed save being risky
  docs: Reformat snapshot-revert force reasons
  docs: Add snapshot-revert qemu managedsave force

 docs/manpages/virsh.rst | 39 ++++++++++++++++++++++++---------------
 src/qemu/qemu_driver.c  |  9 +++++++++
 2 files changed, 33 insertions(+), 15 deletions(-)

-- 
2.24.1


--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list