Skip to content

Commit

Permalink
persistent TPM & UEFI, corrections
Browse files Browse the repository at this point in the history
Signed-off-by: Ian Bishop <[email protected]>
  • Loading branch information
ianb-mp committed Dec 10, 2024
1 parent 78a2507 commit 45e5f6b
Showing 1 changed file with 1 addition and 5 deletions.
6 changes: 1 addition & 5 deletions docs/compute/persistent_tpm_and_uefi_state.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,7 @@ As of v1.0.0, KubeVirt supports using a PVC to persist those files. KubeVirt usu

## Backend storage

KubeVirt automatically creates backend storage PVCs for VMs that need it. However, to persist TPM and UEFI state, the admin must first enable the `VMPersistentState` feature gate.

If [live migration](live_migration.md) is required, then the `vmStateStorageClass` configuration parameter should be set, and must reference a storage class that supports read-write-many (RWX) in filesystem mode (FS).
KubeVirt automatically creates backend storage PVCs for VMs that need it. However, to persist TPM and UEFI state, the admin must first enable the `VMPersistentState` feature gate. `vmStateStorageClass` may be used to manually specify a storage class, otherwise the default storage class will be used.

Here's an example of KubeVirt CR that sets both:
```yaml
Expand All @@ -25,8 +23,6 @@ spec:
```
### Notes:
- If no storage class is specified, the default storage class will be used
- If the storage class has a storage profile that indicates it only supports read-write-once (RWO) then a RWO PVC will be created and the VMI will be marked as non-migratable.
- Backend storage is currently incompatible with VM snapshot. It is planned to add snapshot support in the future.
## TPM with persistent state
Expand Down

0 comments on commit 45e5f6b

Please sign in to comment.