Bug 2318414 - Cloned Debian VM does not start
Summary: Cloned Debian VM does not start
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-boxes
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Christophe Fergeau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-13 15:21 UTC by Joachim Katzer
Modified: 2025-12-16 17:16 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 17:16:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-boxes issues 1108 0 None opened Cloned Debian VM does not start due to incorrect hard disk configuration 2024-10-14 15:52:33 UTC

Description Joachim Katzer 2024-10-13 15:21:34 UTC
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).

Comment 1 Joachim Katzer 2024-10-13 15:24:01 UTC
Host System is: Fedora 41 Beta Silverblue with layered packages boxes and virt-manager.

Comment 2 Adam Williamson 2024-10-14 15:52:33 UTC
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.

Comment 3 Adam Williamson 2025-12-02 01:21:41 UTC
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.

Comment 4 Samyak Jain (RedHat) 2025-12-16 17:16:08 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 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.


Note You need to log in before you can comment on or make changes to this bug.