Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Hi, when taking a snapshot of an UEFI VM, I get "Creating VM snapshot: xxx failed due to Create VM snapshot failed due to org.libvirt.LibvirtException: Operation not supported: internal snapshots of a VM with pflash based firmware are not supported"
Understand this is a limitation of libvirt that it cannot snapshot the pflash based firmware/NVRAM while the instance is running. I can only take snapshot if I power off the instance.
But I also read that recent version of libvirt does support live instance snapshot if it is using qcow2 format firmware. Is there something I can configure in CloudStack to change this so that live snapshot of UEFI instance work?
Thanks

You must be logged in to vote

Replies: 5 comments · 9 replies

Comment options

Ok, answering my own question (partially), so if I leave "snapshot memory" off, I can take an instance snapshot while it is running. But still the question remains, if I have an UEFI instance in cloudstack, I cannot take a disk+memory snapshot of the instance?

You must be logged in to vote
7 replies
@DaanHoogland
Comment options

I have never tried it (consciously). So I will have to test it, I have no idea really. I will try to find (someone to make) time to do it. By the looks of your error message it looks like a libvirt limitation, btw. so what version are you using?

@chunkyen
Comment options

I am using 4.22 KVM Ubuntu 24. Thanks

@DaanHoogland
Comment options

iirc that uses libvirt 10.0, right?

@slavkap
Comment options

slavkap Jan 15, 2026
Collaborator

Hi @chunkyen, @DaanHoogland, from what I found this is supported in libvirt 10.9 (for taking snapshots) and in 10.10 is included support for delete/revert
https://bugzilla.redhat.com/show_bug.cgi?id=1881850#c19
virt-manager/virt-manager#851 (comment)

@jgotteswinter
Comment options

I can test this with Libvirt 11, will report my results

Comment options

@jgotteswinter Do you have any results yet to report?

You must be logged in to vote
1 reply
@jgotteswinter
Comment options

I am working on adding a new hardware generation to our automation where i can test this. Its wip, but finished very soon

Comment options

The problem still exists independent on the version of libvirt. I tried libvirt 11.10.0

The issue is the format of the nvram disk file. I converted it from raw to qcow2 and can now take snapshots with memory of VMs with UEFI.

Here are my changes in the XML config:
from:
<nvram template='/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd' templateFormat='raw' format='**raw**'>/var/lib/libvirt/qemu/nvram/a5b15197-6388-4bc8-a4f4-c446d28fde7c.fd</nvram>
to:
<nvram template='/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd' templateFormat='raw' format='**qcow2**'>/var/lib/libvirt/qemu/nvram/a5b15197-6388-4bc8-a4f4-c446d28fde7c.**qcow2**.fd</nvram>

You must be logged in to vote
1 reply
@DaanHoogland
Comment options

@ingox , does this mean it is to be fixed in an issue (in libvirt)?

Comment options

@DaanHoogland This would need to be fixed in CloudStack. At least it worked with libvirt 11.10.0. I haven't tested the format change (raw to qcow2) with older versions of libvirt.

You must be logged in to vote
0 replies
Comment options

as @rajujith suggested, we may have to first create a folder structure per vm in primary storage like in vmware , just to organise vm files.
the issue with vTPM could be fixed in the same way #11842

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
6 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.