Bug 1936164
| Summary: | Enable KVM Software TPM by default | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Arik <ahadas> |
| Component: | BLL.Virt | Assignee: | Milan Zamazal <mzamazal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tamir <tamir> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4.5 | CC: | bugs |
| Target Milestone: | ovirt-4.4.6 | Flags: | pm-rhel:
ovirt-4.4+
|
| Target Release: | 4.4.6.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.4.6.4 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-05 05:36:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1933974 | ||
| Bug Blocks: | |||
|
Description
Arik
2021-03-07 09:17:40 UTC
Verified on RHV 4.4.6-5. All looks good to me.
Env:
- Engine instance with RHV 4.4.6-5 (ovirt-engine-4.4.6.5-447.gd80dda7.9.el8ev) and RHEL 8.4 installed.
- 3 hosts with RHV 4.4.6-5 and RHEL 8.4, vdsm-4.40.60.4-1.el8ev
Steps:
In Admin Portal:
1. Create a 4.6 data center and a 4.6 cluster.
2. Install a host and create a new NFS storage domain.
3. Create a VM with disk and bios type UEFI and with TPM enabled.
4. Run the VM.
5. Check that there is a tpm tag in the VM XML.
6. Check that the TPM device is listed as one of the vm's devices in the DB.
Results (As Expected):
1. The 4.6 data center and the 4.6 cluster were created.
2. The host was installed and the NFS storage domain was created.
3. The VM was created.
4. The VM is running.
5. The TPM tag exists:
<tpm model='tpm-crb'>
<backend type='emulator' version='2.0'/>
<alias name='ua-f948fd5d-83ad-45c8-9dfe-5e1cb367637d'/>
</tpm>
6. The TPM device is listed as one of the vm's devices in the DB.
Also checked the test case below with a success:
Steps:
In Admin Portal:
1. Create a 4.5 data center and a 4.5 cluster.
2. Install a host and create a new NFS storage domain.
3. Create a VM with disk and bios type UEFI, custom compatibility version 4.6 and with TPM enabled.
4. Run the VM.
5. Check that there is a tpm tag in the VM XML.
6. Check that the TPM device is listed as one of the vm's devices in the DB.
Results (As Expected):
1. The 4.5 data center and the 4.5 cluster were created.
2. The host was installed and the NFS storage domain was created.
3. The VM was created.
4. The VM is running.
5. The TPM tag exists:
<tpm model='tpm-crb'>
<backend type='emulator' version='2.0'/>
<alias name='ua-f948fd5d-83ad-45c8-9dfe-5e1cb367637d'/>
</tpm>
6. The TPM device is listed as one of the vm's devices in the DB.
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |