There are 2 examples of use of <encryption> which uses a 'type' attribute rather than 'format' as documented in the XML schema:
<define name='encryption'> <element name='encryption'> <attribute name='format'> <choice> <value>default</value> <value>qcow</value> <value>luks</value> </choice> </attribute> <interleave> <ref name='secret'/> <optional> <element name='cipher'> <ref name='keycipher'/> </element> <element name='ivgen'> <ref name='keyivgen'/> </element> </optional> </interleave> </element> </define> This also matches what virStorageEncryptionParseNode() is doing. Signed-off-by: Christophe Fergeau <cferg...@redhat.com> --- docs/formatdomain.html.in | 2 +- docs/formatstorage.html.in | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 0e3799061d..4052eb2528 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -2761,7 +2761,7 @@ <write_iops_sec>100000</write_iops_sec> </iotune> <boot order='2'/> - <encryption type='...'> + <encryption format='...'> ... </encryption> <shareable/> diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in index 2a7604d136..dd2f27e54c 100644 --- a/docs/formatstorage.html.in +++ b/docs/formatstorage.html.in @@ -761,7 +761,7 @@ <mtime>1341930622.047245868</mtime> <ctime>1341930622.047245868</ctime> </timestamps> - <encryption type='...'> + <encryption format='...'> ... </encryption> <compat>1.1</compat> -- 2.21.0 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list