diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in index cf36f6cc7b23ce424fe7280cb8e3c1d41444a8b4..aa61ee5cedea90d44deb6807e8627b5b0e0c5234 100644 --- a/docs/drvqemu.html.in +++ b/docs/drvqemu.html.in @@ -519,6 +519,36 @@ mount -t cgroup none /dev/cgroup -o devices <qemu:env name='QEMU_ENV' value='VAL'/> </qemu:commandline> </domain> + + +
+ In some cases e.g. when developing a new feature or for testing it may
+ be required to control a given qemu feature (or qemu capability) to test
+ it before it's complete or disable it for debugging purposes.
+ Since 5.5.0 it's possible to use the same
+ special qemu namespace as above
+ (http://libvirt.org/schemas/domain/qemu/1.0
) and use
+ <qemu:capabilities>
element to add
+ (<qemu:add capability="capname"/>
) or remove
+ (<qemu:del capability="capname"/>
) capability bits.
+ The naming of the feature bits is the same libvirt uses in the status
+ XML. Note that this feature is meant for experiments only and should
+ _not_ be used in production.
+
Example:
+<domain type='qemu' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> + <name>testvm</name> + + [...] + + <qemu:capabilities> + <qemu:add capability='blockdev'/> + <qemu:del capability='drive'/> + </qemu:capabilities> +</domain>