Description of problem: Snapshot creation is failing for VM having vGPU. ~~~ 2021-03-15 16:12:42,578+03 INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default task-590) [376d2ee9-aaaa-4df2-bbbb-e2e60ccf96ed] Lock Acquired to object 'EngineLock:{exclusiveLocks='[8c6a5113-xxxx-4ae2-yyyy-1b852dca6ca3=VM]', sharedLocks=''}' 2021-03-15 16:12:42,580+03 WARN [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default task-590) [376d2ee9-aaaa-4df2-bbbb-e2e60ccf96ed] Validation of action 'CreateSnapshotForVm' failed for user xyz. Reasons: VAR__ACTION__CREATE,VAR__TYPE__SNAPSHOT,ACTION_TYPE_FAILED_VM_USES_MDEV_TYPE_HOOK 2021-03-15 16:12:42,580+03 INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default task-590) [376d2ee9-aaaa-4df2-bbbb-e2e60ccf96ed] Lock freed to object 'EngineLock:{exclusiveLocks='[8c6a5113-xxxx-4ae2-yyyy-1b852dca6ca3=VM]', sharedLocks=''}' 2021-03-15 16:12:42,584+03 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-590) [] Operation Failed: [Cannot create Snapshot. VM uses mdev_type hook.] ~~~ Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create A VM in the Red Hat Virtualization environment. 2. Assign vGPU to the VM. 3. Try to create a snapshot. Actual results: Snapshot creation fail. Expected results: Snapshot should create successfully. Additional info: 1. Who is the customer behind the request? Ans: IBA Ltd Account number - 5649444 2. Why does the customer need this? (List the business requirements here) Ans: Want to create a snapshot of VM without disabling mdev_type and without reboot it. 3. How would the customer like to achieve this? (List the functional requirements here) Ans: We want to use the current functionality without error "Cannot create Snapshot. VM uses mdev_type hook" 4. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? Ans: RHV 4.4 5. Is the sales team involved in this request and do they have any additional input? Ans: No. 6. Would the customer be able to assist in testing this functionality if implemented? Ans: Yes.
why did we block it for all snapshots (in bug 1574480) and not only for memory snapshots? I don't see a reason why not to allow disk-only snapshots.
Yeah, seems like a mistake
Verified: ovirt-engine-4.4.6.6-0.10.el8ev vdsm-4.40.60.6-1.el8ev.x86_64 qemu-kvm-5.2.0-15.module+el8.4.0+10650+50781ca0.x86_64 libvirt-daemon-7.0.0-13.module+el8.4.0+10604+5608c2b4.x86_64 host Nvidia drivers: NVIDIA-vGPU-rhel-8.4-460.73.02.x86_64 VM Nvidia drivers(for Windows and Linux): GRID 12.0 GA Verification scenario: 1. Run RHEL VM with secure boot and mdev enrolled keys. 2. Create snapshot with memory. Verify action is rejected by WebAdmin with the next message: "Cannot create Snapshot. VM uses mdev_type hook" 3. Create snapshot without memory. Verify snapshot created. 4. Power off VM, preview -> commit snapshot. run VM. Verify VM is running with mdev instance. 5. Repeat steps 1-4 with Windows VM.
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 (Moderate: RHV Manager security update (ovirt-engine) [ovirt-4.4.6]), 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/RHSA-2021:2179