Skip to content

CNV-54462 -- vTPM documentation #96528

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: enterprise-4.17
Choose a base branch
from
+11 −3
Open

CNV-54462 -- vTPM documentation #96528

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions modules/virt-about-vtpm-devices.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,15 @@ the node has one.

A vTPM device also protects virtual machines by storing secrets without physical hardware. {VirtProductName} supports persisting vTPM device state by using Persistent Volume Claims (PVCs) for VMs. You must specify the storage class to be used by the PVC by setting the `vmStateStorageClass` attribute in the `HyperConverged` custom resource (CR):


[IMPORTANT]
====
**vTPM Storage class and live migration considerations**

In {VirtProductName}, if the `storageClass` for `vmStateStorageClass` is not explicitly defined, the system uses the cluster’s default storage class to create the vTPM persistent volume claim (PVC). The access mode for the PVC is determined by the storage profile of the storage class.

VMs with vTPM devices that use an RWO volume are non-migratable. To enable live migration, the underlying storage class for the vTPM PVC must support the ReadWriteMany (RWX) access mode.

[source,yaml]
----
kind: HyperConverged
Expand All @@ -28,8 +37,7 @@ spec:

# ...
----

[NOTE]
====
[NOTE]

The storage class must be of type `Filesystem` and support the `ReadWriteMany` (RWX) access mode.
====