* into S4 state (also known as hibernation) unless you also modify the
* persistent domain definition.
*
+ * The supplied XML description of the device should be as specific
+ * as its definition in the domain XML. The set of attributes used
+ * to match the device are internal to the drivers. Using a partial definition,
+ * or attempting to detach a device that is not present in the domain XML,
+ * but shares some specific attributes with one that is present,
+ * may lead to unexpected results.
+ *
* Returns 0 in case of success, -1 in case of failure.
*/
int
* into S4 state (also known as hibernation) unless you also modify the
* persistent domain definition.
*
+ * The supplied XML description of the device should be as specific
+ * as its definition in the domain XML. The set of attributes used
+ * to match the device are internal to the drivers. Using a partial definition,
+ * or attempting to detach a device that is not present in the domain XML,
+ * but shares some specific attributes with one that is present,
+ * may lead to unexpected results.
+ *
* Returns 0 in case of success, -1 in case of failure.
*/
int
For passthrough host devices, see also B<nodedev-reattach>, needed if
the device does not use managed mode.
-B<Note>: using of partial device definition XML files may lead to unexpected
-results as some fields may be autogenerated and thus match devices other than
-expected.
+B<Note>: The supplied XML description of the device should be as specific
+as its definition in the domain XML. The set of attributes used
+to match the device are internal to the drivers. Using a partial definition,
+or attempting to detach a device that is not present in the domain XML,
+but shares some specific attributes with one that is present,
+may lead to unexpected results.
If I<--live> is specified, affect a running domain.
If I<--config> is specified, affect the next startup of a persistent domain.