[libvirt] [PATCH 2/3] lib: Clarify that any block job may block VM save or device detach
The documentation was only referring to a copy job, but in fact any
running blockjob will have the same results.
Signed-off-by: Peter Krempa <pkrempa(a)redhat.com>
---
src/libvirt-domain.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/libvirt-domain.c b/src/libvirt-domain.c
index c155b36e16..92a095f00b 100644
--- a/src/libvirt-domain.c
+++ b/src/libvirt-domain.c
@@ -883,8 +883,8 @@ virDomainSave(virDomainPtr domain, const char *to)
* virDomainSaveImageGetXMLDesc() and virDomainSaveImageDefineXML().
*
* Some hypervisors may prevent this operation if there is a current
- * block copy operation; in that case, use virDomainBlockJobAbort()
- * to stop the block copy first.
+ * block job running; in that case, use virDomainBlockJobAbort()
+ * to stop the block job first.
*
* Returns 0 in case of success and -1 in case of failure.
*/
@@ -8297,8 +8297,8 @@ virDomainDetachDevice(virDomainPtr domain, const char *xml)
* persisted device allocation.
*
* Some hypervisors may prevent this operation if there is a current
- * block copy operation on the device being detached; in that case,
- * use virDomainBlockJobAbort() to stop the block copy first.
+ * block job running operation on the device being detached; in that case,
+ * use virDomainBlockJobAbort() to stop the block job first.
*
* Beware that depending on the hypervisor and device type, detaching a device
* from a running domain may be asynchronous. That is, calling
--
2.20.1