-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
2.7.10, 2.8.0
-
Quality / Stability / Reliability
-
2
-
False
-
-
True
-
Release Notes
-
RN 2.8.0
-
Known Issue
-
In Progress
-
-
Description of problem:
Migrate win2022 VM with BIOS(without TPM device) from vSphere to OCP cluster, the TPM device is added to target VM
Version-Release number of selected component (if applicable):
MTV 2.7.10-4 with CNV 4.17.4; MTV 2.8.0-32 (IIB: 938251) with CNV 4.17.6; MTV 2.8.0-37 (IIB: 943612) with CNV 4.18.1(IIB: 936668)
How reproducible:
100%
Steps to Reproduce:
1. Create a win 2022 VM in vSphere7 with BIOS without tpm device
2. Create warm migration plan: mtv-win2022-bios to migrate VM: mtv-function-win2022 from vSphere7, the plan executed successfully.
3. Check the VM yaml file: devices: tpm: persistent:false and fireware: bootloader: bios:{ }
4. Login to win2022 VM, check there is tpm2.0 and the device cannot start
Actual results:
In step2,3, the tpm device is added to target win2022 VM
Expected results:
In step2,3, the tpm device is not added to target win2022 VM
- blocks
-
-
- Closed
-
- depends on
-
-
- Closed
-
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is documented by
-
MTV-2033 [DOC] Release Notes for MTV 2.8.0
-
- Closed
-
- mentioned on
