-
Bug
-
Resolution: Done
-
Undefined
-
None
-
CNV v4.17.6, CNV v4.17.8
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
Description of problem:
Warm migrate windows 2022 VM with BIOS(without TPM device) from vSphere7 to OCP cluster,
plan executed successfully, after migration check the VM yaml file without tpm device, and with firmware: bootloader: bios:{ },
but there is PVC:"persistent-state-for-mtv-function-win2022" , with storage_class: ocs-storagecluster-ceph-rbd-virtualization, which indicate the VM with tpm: persistent: true in Openshift Virtualization,
login to VM, there is tpm device and the device cannot start as tpm don't work with bios.
Version-Release number of selected component (if applicable):
MTV 2.8.0-32 (IIB: 938251) with CNV 4.17.6 MTV 2.8.1-5 (IIB: 953510) with CNV 4.17.8 (IIB: 950649)
How reproducible:
100%
Steps to Reproduce:
1) Create a win2022 vm: mtv-function-win2022 with bios, and without vtpm in vSphere 7
2) Create a warm migration plan to migrate win2022 vm to CNV cluster, the plan executed successfully
3) Check the VM is running, check the VM Yaml file without tpm device and with
" firmware: bootloader: bios: {}", but there is pvc: "persistent-state-for-mtv-function-win2022" created during the VirtualMachineCreation phase. More details in attached files: mtv-function-win2022-ocp-4-17.yaml
4) Login to VM, there is tpm device and the device cannot start as tpm don't work with bios.
- blocks
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
