External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-10-05 22:05:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Reformat snapshot-revert force reasons

Browse Source 
Reformat explanations of the snapshot-revert force reasons in
preparation for more to be added. This is a simple reformat without any
wording changes.

Signed-off-by: Michael Weiser <michael.weiser@gmx.de>
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Michael Weiser 2020-01-03 19:43:24 +01:00 committed by Michal Privoznik
parent 5373f63b30
commit 29773f2a75
1 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/manpages/virsh.rst
View File

@ -6971,20 +6971,22 @@ transient domains cannot be inactive, it is required to use one of these
flags when reverting to a disk snapshot of a transient domain. flags when reverting to a disk snapshot of a transient domain.
There are two cases where a snapshot revert involves extra risk, which There are two cases where a snapshot revert involves extra risk, which
requires the use of *--force* to proceed. One is the case of a requires the use of *--force* to proceed:
snapshot that lacks full domain information for reverting
configuration (such as snapshots created prior to libvirt 0.9.5); * One is the case of a snapshot that lacks full domain information for
since libvirt cannot prove that the current configuration matches what reverting configuration (such as snapshots created prior to libvirt
was in use at the time of the snapshot, supplying *--force* assures 0.9.5); since libvirt cannot prove that the current configuration matches
libvirt that the snapshot is compatible with the current configuration what was in use at the time of the snapshot, supplying *--force* assures
(and if it is not, the domain will likely fail to run). The other is libvirt that the snapshot is compatible with the current configuration
the case of reverting from a running domain to an active state where a (and if it is not, the domain will likely fail to run).
new hypervisor has to be created rather than reusing the existing
hypervisor, because it implies drawbacks such as breaking any existing * The other is the case of reverting from a running domain to an active
VNC or Spice connections; this condition happens with an active state where a new hypervisor has to be created rather than reusing the
snapshot that uses a provably incompatible configuration, as well as existing hypervisor, because it implies drawbacks such as breaking any
with an inactive snapshot that is combined with the *--start* or existing VNC or Spice connections; this condition happens with an active
*--pause* flag. snapshot that uses a provably incompatible configuration, as well as with
an inactive snapshot that is combined with the *--start* or *--pause*
flag.
snapshot-delete snapshot-delete