Description of problem: With a freshly installated Fedora 32 (Workstation) system, gnome-boxes does not have all the necessary dependecies installated. Version-Release number of selected component (if applicable): 3.36.5 (latest available with Fedora 32) How reproducible: I have installed Fedora 32 multiple times and always have encountered this issue. Steps to Reproduce: 1. Perform a fresh installation of Fedora 32 Workstation and update the system. 2. Open GNOME Boxes so that it performs its initialization. Then close the application. 3. Run the command `gnome-boxes --checks'. Actual results: The command output is as follows: $ gnome-boxes --checks (gnome-boxes:76903): Boxes-WARNING **: 16:37:48.385: util-app.vala:367: Failed to execute child process ?virsh? (No such file or directory) • The CPU is capable of virtualization: yes • The KVM module is loaded: yes • Libvirt KVM guest available: no • Boxes storage pool available: no Could not get “gnome-boxes” storage pool information from libvirt. Make sure “virsh -c qemu:///session pool-dumpxml gnome-boxes” is working. • The SELinux context is default: yes Report bugs to <http://gitlab.gnome.org/gnome/gnome-boxes/issues>. Boxes home page: <https://wiki.gnome.org/Apps/Boxes>. Expected results: $ gnome-boxes --checks • The CPU is capable of virtualization: yes • The KVM module is loaded: yes • Libvirt KVM guest available: yes • Boxes storage pool available: yes • The SELinux context is default: yes Report bugs to <http://gitlab.gnome.org/gnome/gnome-boxes/issues>. Boxes home page: <https://wiki.gnome.org/Apps/Boxes>. Additional info: The issue is resolved when installating the two packages `libvirt-client' and `virtdetect'. I may suggest adding these as dependencies to gnome-boxes.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This issue still occurs on Fedora 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.
This issue still occurs on Fedora 37.
Just have gotten the same issue with a fresh Fedora 37 install. Installing `libvirt-client' and `virtdetect' has helped as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2162816 opened to track this for Fedora 37.