External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-22 04:25:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Extend TPM docs with new encryption element

Browse Source 
Describe the encryption element in the TPM's domain XML.

Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Stefan Berger 2019-07-25 14:22:15 -04:00 committed by Daniel P. Berrangé
parent a90f98c071
commit b2f6a5c688
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/formatdomain.html.in
View File

@ -8215,6 +8215,9 @@ qemu-kvm -net nic,model=? /dev/null
TPM functionality for each VM. QEMU talks to it over a Unix socket. With TPM functionality for each VM. QEMU talks to it over a Unix socket. With
the emulator device type each guest gets its own private TPM. the emulator device type each guest gets its own private TPM.
<span class="since">'emulator' since 4.5.0</span> <span class="since">'emulator' since 4.5.0</span>
The state of the TPM emulator can be encrypted by providing an
<code>encryption</code> element.
<span class="since">'encryption' since 5.6.0</span>
</p> </p>
<p> <p>
Example: usage of the TPM Emulator Example: usage of the TPM Emulator
@ -8224,6 +8227,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;devices&gt; &lt;devices&gt;
&lt;tpm model='tpm-tis'&gt; &lt;tpm model='tpm-tis'&gt;
&lt;backend type='emulator' version='2.0'&gt; &lt;backend type='emulator' version='2.0'&gt;
&lt;encryption secret='6dd3e4a5-1d76-44ce-961f-f119f5aad935'/&gt;
&lt;/backend&gt; &lt;/backend&gt;
&lt;/tpm&gt; &lt;/tpm&gt;
&lt;/devices&gt; &lt;/devices&gt;
@ -8286,6 +8290,14 @@ qemu-kvm -net nic,model=? /dev/null
<li>'2.0' : creates a TPM 2.0</li> <li>'2.0' : creates a TPM 2.0</li>
</ul> </ul>
</dd> </dd>
<dt><code>encryption</code></dt>
<dd>
<p>
The <code>encryption</code> element allows the state of a TPM emulator
to be encrypted. The <code>secret</code> must reference a secret object
that holds the passphrase from which the encryption key will be derived.
</p>
</dd>
</dl> </dl>
<h4><a id="elementsNVRAM">NVRAM device</a></h4> <h4><a id="elementsNVRAM">NVRAM device</a></h4>