After creating a clone of VM (Debian-12), the clone does not start because it can't mount its virtual hard disks. The original VM has a virtio device: <target dev="vda" bus="virtio"/> <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/> But the clone gets mistakenly a SATA device: <target dev="sda" bus="sata"/> <address type="drive" controller="0" bus="0" target="0" unit="0"/> In Debian the system partition is configured as: /dev/vda5 /mnt/btr_pool ... Reproducible: Sometimes Steps to Reproduce: 1. Clone a VM (in GNOME-Boxes) 2. Select the clone and start it 3. Check if it is starting Actual Results: A Debian-12 clone does not start, because of the different device configuration. A Fedora Silverblue clone does start despite of the different device configuration. Expected Results: A clone of a VM should have the same device configuration as the original and should boot without errors (provided the original could do it).
Host System is: Fedora 41 Beta Silverblue with layered packages boxes and virt-manager.
Thanks for the report! Since GNOME devs tend to prefer upstream tickets, I've filed https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/1108 for you - if you could look out for any follow up there it'd be great.
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. 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 '41'. 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 41 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.