Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Release: RHEL 8, all
Upstream Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1881850
Description of problem: Error message when invoking the creation of a snapshot while secure loader with UEFI is enabled.
How reproducible:
Those combinations are allowed in an XML file while the host is an EFI systen, at the state of creation of a VM in virt-manager:
option 1:
<os>
<type arch="x86_64" machine="q35">hvm</type>
<boot dev="hd"/>
<loader secure="yes"/>
</os>
option 2:
<os>
<type arch="x86_64" machine="q35">hvm</type>
<loader readonly="yes" type="pflash" secure="yes">/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader>
<boot dev="hd"/>
</os>
option 3:
<os>
<type arch="x86_64" machine="q35">hvm</type>
<loader readonly="yes" type="pflash" secure="yes">/usr/share/edk2/ovmf/OVMF_CODE.fd</loader>
<boot dev="hd"/>
</os>
Option 1 is allowed.
Steps to Reproduce:
1. Set either option 2 or 3;
2. Attempt a creation a snapshot.
Actual results:
<os>
<type arch="x86_64" machine="pc-q35-4.2">hvm</type>
<loader readonly="yes" type="pflash">/usr/share/edk2/ovmf/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/fedora32_VARS.fd</nvram>
<boot dev="hd"/>
</os>
Message error through virt-manager:
"Error creating snapshot: Operation not supported: internal snapshots of a VM with pflash based firmware are not supported
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/details/snapshots.py", line 239, in _do_create_snapshot
self.vm.create_snapshot(xml)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1057, in create_snapshot
self._backend.snapshotCreateXML(xml, flags)
File "/usr/lib64/python3.8/site-packages/libvirt.py", line 2801, in snapshotCreateXML
if ret is None:raise libvirtError('virDomainSnapshotCreateXML() failed', dom=self)
libvirt.libvirtError: Operation not supported: internal snapshots of a VM with pflash based firmware are not supported"
Expected results: options matching UEFI systems, 2 and 3, to be allowed.
What is the business impact?
Reduced functionality for users moving to Windows 11 KVM using UEFI.
Comment 2Jaroslav Suchanek
2022-09-21 08:38:30 UTC
*** This bug has been marked as a duplicate of bug 1436245 ***