Description of problem: Currently it's not possible to snaphsot the <nvram> backing image while taking an external snapshots. Add the support so that all files are properly versioned.
hi, Peter, From the libvirt.org[1], <mvram> is one specific device for PPC arch. So, I'd like to update the arch of this BZ from "Unspecified" to "ppc64le" for better tracking. Is it ok for you? Please correct me if any of my thoughts is wrong. [1] nvram device: http://libvirt.org/formatdomain.html#elementsNVRAM
No, <nvram> is also used for OVMF, which maps to a second pflash drive. So it certainly is not ppc64 relevant at all. The ppc64 nvram probably won't be snapshottable, but I did not investiagte further.
(In reply to Peter Krempa from comment #2) > No, <nvram> is also used for OVMF, which maps to a second pflash drive. So > it certainly is not ppc64 relevant at all. The ppc64 nvram probably won't > be snapshottable, but I did not investiagte further. OK, it seesm the <nvram> in this BZ is the following settings in <os>, not the specific device for PPC. <os> ...... <nvram template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/nvram/guest_VARS.fd</nvram> ...... </os>
Comment 5 should include answers from comment 4.
This bug is going to be addressed in next major release.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Reopen this bug according to the comment 13.
*** Bug 2128504 has been marked as a duplicate of this bug. ***