I think virt-clone in Fedora 39 tries to generate a qcow2 file called xxxx_VARS.fd instead of xxxx_VARS.qcow2. virt-clone --reflink used to work (I think last good was in Fedora 38, not 100% sure though) and now it only works if there isn't an NVRAM file. If there is one then the HD image copies ok, but virt-clone crashes when trying to copy the NVRAM file. Reproducible: Always Steps to Reproduce: 1. install Fedora 39 with (at least) /var/lib/libvirt as btrfs 2. run virt-install to make a VM called (say) "dec30" 3. virt-clone --original dec30 --name dec30-pristine --reflink --file /var/lib/libvirt/images/dec30-pristine.img Actual Results: HD image file copies with --relink just fine. NVRAM file doesn't copy, instead I get this slightly strange error message: ERROR Couldn't create storage volume 'dec30-pristine_VARS.fd': 'unsupported flags (0x2) in function storageBackendCreateQemuImg' Expected Results: dec30-pristine_VARS.qcow2 in /var/lib/libvirt/qemu/nvram If I mv dec30_VARS.qcow2 aside the virt-clone operation succeeds (albeit without an nvram file, but it looks like the VM reboots on first boot generating a qcow2 file called dec30-pristine_VARS.fd) Looks like a bug to me!
This is likely related to bz#1324006. Thanks "minimal" on IRC :-) I'll note my HD images are indeed in raw format, and a way to ask virt-install (and virt-clone) to retain the old raw format for the nvram files would be sufficient for me.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. 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 '39'. 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 39 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-2024-eb0b085f84 (virt-manager-5.0.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-eb0b085f84
FEDORA-2024-eb0b085f84 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-eb0b085f84` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-eb0b085f84 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-eb0b085f84 (virt-manager-5.0.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.