- 
    
Bug
 - 
    Resolution: Done
 - 
    
Undefined
 - 
    None
 - 
    CNV v4.18.1, CNV v4.18.2
 - 
    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-p6c2b, 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 with CNV 4.18.1, 4.18.2(IIB 949737)
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-p6c2b" created during the VirtualMachineCreation phase. More details in attached files: mtv-function-win2022.yaml, pvc
$ oc get pvc -A |grep win2022
mtv-test                   persistent-state-for-mtv-function-win2022-p6c2b   Bound    pvc-1ef78797-865a-4651-9bab-ca46e079dbce   10Mi          RWO            ocs-storagecluster-ceph-rbd-virtualization   <unset>                 4s
4) Login to VM, there is tpm device and the device cannot start as tpm don't work with bios.

Actual results:
In step3: There is pvc: persistent-state-for-mtv-function-win2022-p6c2b with storage class: ocs-storagecluster-ceph-rbd-virtualization In step4: There is tpm device and the device cannot start as tpm don't work with bios
Expected results:
In step3: No PVC is created for vtpm vtpm persistent-state In step4: No tpm device in VM
- blocks
 - 
                    
CNV-55614 [4.17.3] VMCP for Windows VMs has "preferredTPM: persistent: true" preventing VM from starting if VM does not have TPM
-         
 - Closed
 
 -         
 - 
                    
MTV-2049 vTPM is added by default for win2022 bios VM after migration
-         
 - Closed
 
 -         
 
- duplicates
 - 
                    
CNV-60467 [v4.18.3] No way of overriding the preference value of PreferredTPM from within a VirtualMachine
-         
 - Closed
 
 -         
 
- is blocked by
 - 
                    
MTV-2014 MTV should not request a VM with vTPM enabled if the original one did not had vTPM
-         
 - Closed
 
 -