Bug 1936164 - Enable KVM Software TPM by default
Summary: Enable KVM Software TPM by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.4.6
: 4.4.6.4
Assignee: Milan Zamazal
QA Contact: Tamir
URL:
Whiteboard:
Depends On: 1933974
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-07 09:17 UTC by Arik
Modified: 2021-05-05 05:36 UTC (History)
1 user (show)

Fixed In Version: ovirt-engine-4.4.6.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-05 05:36:00 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 112279 0 master MERGED core: Enable TPM devices 2021-03-14 14:33:09 UTC
oVirt gerrit 113634 0 master MERGED api: introduce tpm device 2021-04-12 07:41:19 UTC
oVirt gerrit 113972 0 master MERGED Upgrade to model 4.4.27 2021-03-22 09:01:54 UTC

Description Arik 2021-03-07 09:17:40 UTC
Enable KVM Software TPM by default as from cluster level 4.6

Comment 1 Tamir 2021-04-22 13:52:05 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.

Comment 2 Sandro Bonazzola 2021-05-05 05:36:00 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.