-
Bug
-
Resolution: Done
-
Critical
-
None
MTV should not request a VM with vTPM enabled if the original one did not had vTPM to avoid situations like in https://issues.redhat.com/browse/CNV-55614
- blocks
-
MTV-1859 Some windows guests can't start on MTV if the guests are migrated from vsphere provider
-
- Closed
-
-
CNV-55375 Persistent vTPM is added by default for win2022 bios VM after migration - OCP4.16
-
- Closed
-
-
MTV-2049 vTPM is added by default for win2022 bios VM after migration
-
- Closed
-
-
CNV-59724 vTPM is added by default for win2022 bios VM after migration - OCP 4.18
-
- Closed
-
-
CNV-59727 vTPM is added by default for win2022 bios VM after migration - OCP 4.17
-
- Closed
-
- is blocked by
-
CNV-58447 No way of overriding the preference value of PreferredTPM from within a VirtualMachine
-
- Verified
-
-
CNV-60467 [v4.18.3] No way of overriding the preference value of PreferredTPM from within a VirtualMachine
-
- Closed
-
-
CNV-60468 [v4.17.7] No way of overriding the preference value of PreferredTPM from within a VirtualMachine
-
- Closed
-
-
CNV-60469 [v4.16.7] No way of overriding the preference value of PreferredTPM from within a VirtualMachine
-
- Closed
-
-
MTV-2049 vTPM is added by default for win2022 bios VM after migration
-
- Closed
-
-
CNV-59313 [v4.19.0] No way of overriding the preference value of PreferredTPM from within a VirtualMachine
-
- Closed
-