Bug 2136180
| Summary: | cloning vm fails when cloning "Windows 2022" guest from snapshot with TPM device enabled | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marian Jankular <mjankula> |
| Component: | ovirt-engine | Assignee: | Milan Zamazal <mzamazal> |
| Status: | CLOSED ERRATA | QA Contact: | Tamir <tamir> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.5.2 | CC: | ahadas, emarcus, lsurette, mavital, mperina, mtessun, mzamazal, pelauter, srevivo, ycui |
| Target Milestone: | ovirt-4.5.3-async | Keywords: | PrioBumpPM |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.5.3.3 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, certain operations on VMs with TPM devices, such as exporting a VM to a data domain or cloning a VM from a snapshot, sometimes incorrectly disabled the TPM device in the target VM. This not only caused losing the TPM device, but also prevented performing the operations for VMs with mandatory TPM devices (such as VMs running modern Windows versions).
In this release, the TPM devices remain enabled and the given VM operations work.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-30 07:53:04 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: | |||
|
Description
Marian Jankular
2022-10-19 14:22:30 UTC
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).
Verified on RHV 4.5.3-5.
Env:
- Engine instance with RHV 4.5.3-5 (ovirt-engine-4.5.3.3-1.el8ev) and RHEL 8.6 installed.
- A host with RHV 4.5.3-5 and RHEL 8.6 and with vdsm-4.50.3.5-1.el8ev.
Steps:
1. Create a 4.7 data center and a 4.7 cluster.
2. Install the hosts and create a new NFS storage domain.
3. Create a VM from RHEL 8 template, with a disk, chipset set as "Q35 Chipset with UEFI", TPM enabled, and OS set as "Windows 2022".
4. Run the VM.
5. Install the tpm2-tools package.
6. Create a file with text.
7. Encrypt the created file using a loaded key from the TPM.
8. Shutdown the VM.
9. Snapshot the VM (with disk and memory).
10. Clone the VM from the created snapshot.
11. Run the cloned VM.
12. Decrypt the encrypted file.
Results (As Expected):
1. The 4.7 data center and the 4.7 cluster were created.
2. The hosts were installed, and the NFS storage domain was created.
3. The VM was created.
4. The VM was running.
5. The tpm2-tools package was installed.
6. The file was created.
7. The file was encrypted.
8. The VM was down.
9. The snapshot was created.
10. The VM was cloned successfully.
11. The VM was running.
12. The file was decrypted successfully.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHV Manager (ovirt-engine) [ovirt-4.5.3-2] update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8695 |