Description of problem: Error message when invoking the creation of a snapshot while secure loader with UEFI is enabled. Version-Release number of component: libvirt-client.x86_64 6.1.0-4.fc32 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.
Snapshotting with UEFI is blocked waiting for improved savevm support in QEMU. This is provided by https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg05221.html which will then need a corresponding libvirt impl
The present report came too early. Format QCOW2 still allows for snaphost in BIOS.
This applies to F34 as well. Any idea when we could have this?
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still happening on Fedora 35 fully updated
reproducible | virt-manager v. 4.0.0; libvirt-daemon-kvm v. 8.1.0
Has there been any movement on this, as we cannot seek to remove MBR/BIOS support when libvirt doesn't allow UEFI snapshots!
The QEMU side for this is done, but the libvirt side is much more work than anticipated, so i had to temporarily put it on the backburner I'm afraid.
How I understand this is that you're planning to exclude nvram from snapshots. That's only necessary if you're using an image format for nvram that doesn't support snapshots (and you're using raw images), the firmware itself is marked as read-only and thus already excluded from snapshots. But... let's say you make a snapshot of a working state of a VM. You then make changes to it, breaking it in the process, and revert to the snapshot. Would you expect it to work afterwards?
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still valid on Fedora 39.