aboutsummaryrefslogtreecommitdiff
path: root/libraries/libvirt/README
diff options
context:
space:
mode:
authorMatteo Bernardini <ponce@slackbuilds.org>2021-05-03 23:04:06 +0200
committerRobby Workman <rworkman@slackbuilds.org>2021-05-04 19:29:31 -0500
commitaafcf41b58046ecb0f0ab7abeb3f845b3cb49f72 (patch)
tree657648eddaeec7fbd50b2c1f2ffb53b18cdb29e9 /libraries/libvirt/README
parent00bf356e7b902470362c2253b93ca873a2ea90b5 (diff)
libraries/libvirt: Updated for version 7.3.0.
Signed-off-by: Matteo Bernardini <ponce@slackbuilds.org>
Diffstat (limited to 'libraries/libvirt/README')
-rw-r--r--libraries/libvirt/README8
1 files changed, 5 insertions, 3 deletions
diff --git a/libraries/libvirt/README b/libraries/libvirt/README
index 471c913f8eff..85c13caec778 100644
--- a/libraries/libvirt/README
+++ b/libraries/libvirt/README
@@ -54,10 +54,12 @@ installed versions of libvirt before this will build.
Note also that sometimes, in consequence of a major-version upgrade,
you might discover that the libvirt configuration is in an inconsistent
-state (machine networking broken and so on) and when this happens you
-might want to consider starting from a clean state. To do this:
+state (machine networking broken and so on) and when this happens and a
+simple reboot won't solve you might want to consider starting from a
+clean state. To do this:
- backup the existing vms files and their configurations too (with
- "virsh dumpxml $name > ${name}.xml)
+ "virsh dumpxml $name > ${name}.xml", check all the *dumpxml commands
+ available with "virsh help")
- remove libvirt
- delete all the system directories (/var/lib/libvirt, /var/log/libvirt,
/etc/libvirt)