Bug 2183626 - Boxes doesn't appear to understand aarch64 machines.
Summary: Boxes doesn't appear to understand aarch64 machines.
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-boxes
Version: rawhide
Hardware: aarch64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Christophe Fergeau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2023-03-31 20:58 UTC by Jeremy Linton
Modified: 2024-06-05 23:15 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:35:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jeremy Linton 2023-03-31 20:58:12 UTC
Description of problem: Clicking the "+" icon with an aarch64 machine, if one selects "Download OS" the only choices are x86_64 and 686 OS choices. Selecting one of them downloads the x86 image (as expected) but of course it can't run it. 

Manually downloading the F38 fedora server .iso image and using "Install from file" and manually clicking Operating System->fedora and UEFI options (the BIOS option doesn't work either and probably shouldn't be visible) just results in a blank boxes screen with just the "+" icon. Nothing seems to be starting or getting added.


Version-Release number of selected component (if applicable): 

gnome-boxes-44.0-1.fc38.aarch64


How reproducible: 100%


Steps to Reproduce:
1. Install a fedora workstation/aarch64
2. Run boxes
3. add VM.

Actual results:

no VM

Expected results:

A VM starts.

Additional info:

Comment 2 Aoife Moloney 2024-05-07 16:03:46 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
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 '38'.

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 38 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 3 Aoife Moloney 2024-05-21 14:35:12 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

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

Comment 4 Davide Cavalca 2024-05-21 22:49:02 UTC
This is still relevant

Comment 5 Jeremy Linton 2024-06-05 23:15:22 UTC
This has been a really low priority thing, but I will respin the upstream patches in the near future, although I had hoped for someone to at least take a look/review them before I updated them with just my own review comments.


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