diff options
| author |   Daniel Veillard <veillard@redhat.com> | 2009-11-18 11:53:41 +0100 |
|---|---|---|
| committer | Daniel Veillard <veillard@redhat.com> | 2009-11-20 16:09:36 +0100 |
| commit | 7d43c80bc4a3713b8f7431796843569d96baaaa8 (patch) | |
| tree | 0c7521e91a913c4cdd92f26352968c962f750dc7 | |
| parent | 504262 Check for duplicated UUID in XM Xen defines (diff) | |
| download | libvirt-7d43c80bc4a3713b8f7431796843569d96baaaa8.tar.gz libvirt-7d43c80bc4a3713b8f7431796843569d96baaaa8.tar.bz2 libvirt-7d43c80bc4a3713b8f7431796843569d96baaaa8.zip | |
514532 Fix man page, most operation are synchronous
* tools/virsh.pod: the man page was stating that most operations
are asynchronous while in fact most of them are synchronous except
domain shutdown, setvcpus and setmem.
| -rw-r--r-- | tools/virsh.pod | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/tools/virsh.pod b/tools/virsh.pod index 55ec64a82..6ff015132 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -40,12 +40,11 @@ Most B<virsh> commands require root privileges to run due to the communications channels used to talk to the hypervisor. Running as non root will return an error. -Most B<virsh> commands act asynchronously, so just because the B<virsh> -program returned, doesn't mean the action is complete. This is -important, as many operations on domains, like create and shutdown, -can take considerable time (30 seconds or more) to bring the machine -into a fully compliant state. If you want to know when one of these -actions has finished you must poll through virsh list periodically. +Most B<virsh> commands act synchronously, except maybe shutdown, +setvcpus and setmem. In those case the fact that the B<virsh> +program returned, may not mean the action is complete and you +must poll periodically to detect that the guest completed the +operation. =head1 GENERIC COMMANDS |