Add a warning and support for TPM #665
Conversation
|
vsphere needs to be verified(mainly the inventory). Also the warning might change to use luks(future?). |
validation/policies/io/konveyor/forklift/vmware/tpm_enabled.rego
Outdated
Show resolved
Hide resolved
the warning would still hold as we won't be able to transfer the data but yeah, we can then extend the warning by saying that luks can be specified as part of the plan when we do that
they support windows 11 so it needs to be persistent |
If the source VM is set with windows 2022 or windows 11 that must have a TPM warn about it. Signed-off-by: Liran Rotenberg <[email protected]>
When having Windows 2k22 or Windows 11 OS, a TPM device is a must. Therefore, we will create it also for the destination VM. The data is persist in ovirt. If supported by kubevirt the TPM will be persistent TPM, otherwise the TPM is without persistent data. In order to have the TPM persistent it is required to have kubvirt v1.0.0 and adding configuration manually as described in: https://kubevirt.io/user-guide/virtual_machines/persistent_tpm_and_uefi_state/ It is also supported in CNV running on OCP 4.14, and you need to follow: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.14/html/virtualization/virtual-machines#virt-using-vtpm-devices Signed-off-by: Liran Rotenberg <[email protected]>
Signed-off-by: Liran Rotenberg <[email protected]>
Warn in case TPM device is detected on a VM. Signed-off-by: Liran Rotenberg <[email protected]>
When having TPM device from the source, create it also for the destination VM. The data is persist in ovirt. If supported by kubevirt the TPM will be persistent TPM, otherwise the TPM without persistent data. Signed-off-by: Liran Rotenberg <[email protected]>
|
ahadas
changed the title
When having a TPM device from the source(oVirt - based on having windows 2022 or windows 11 OS),
create it also for the destination VM.
The data is persist in oVirt. Therefore, if supported by kubevirt the TPM will be persistent TPM,
otherwise the TPM without persistent data.
A warning will be shown as the data will be lost during the migration
In order to have the TPM persistent it is required to have kubvirt
v1.0.0 and adding configuration manually as described in:
https://kubevirt.io/user-guide/virtual_machines/persistent_tpm_and_uefi_state/
It is also supported in CNV running on OCP 4.14, and you need to follow:
https://access.redhat.com/documentation/en-us/openshift_container_platform/4.14/html/virtualization/virtual-machines#virt-using-vtpm-devices
https://issues.redhat.com/browse/MTV-378