From 972f7e6e49c0d8e5f50ba8ce9b6f037ceea8b36b Mon Sep 17 00:00:00 2001 From: Eric Blake Date: Mon, 12 Dec 2011 14:28:31 -0700 Subject: [PATCH] docs: tweak 'virsh edit' wording I was wondering why 'virsh edit' didn't support the same '--inactive' option as 'virsh dumpxml'; reading the source code showed that --inactive was already implied, and that the only way to alter a running guest rather than affecting next boot is by hot-plugging individual devices, or by something complex like saving the guest and modifying the save image. * tools/virsh.pod (define, edit): Mention behavior when guest is already running. --- tools/virsh.pod | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tools/virsh.pod b/tools/virsh.pod index fe927140a8..d56c5d7d6d 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -497,7 +497,8 @@ B =item B I Define a domain from an XML . The domain definition is registered -but not started. +but not started. If domain is already running, the changes will take +effect on the next boot. =item B I @@ -717,11 +718,12 @@ specified, then the output will be escaped for use in XML. =item B I -Edit the XML configuration file for a domain. +Edit the XML configuration file for a domain, which will affect the +next boot of the guest. This is equivalent to: - virsh dumpxml domain > domain.xml + virsh dumpxml --inactive --security-info domain > domain.xml vi domain.xml (or make changes with your other text editor) virsh define domain.xml -- GitLab