-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't launch VM because of "util-app.vala:442: Failed to execute: virsh capabilities" error #85
Comments
Same issue here on Fedora 37 Silverblue. |
Same here on pop os.
|
I think this can be isolated to socket permissions. I can get a similar failure when running
|
+1 This is also happening in Vanilla OS, even after installing the required libs/modules in abroot. Everything works, create button grayed out, same error in shell. |
Not an expert here, but could this be related to version differences for libvirt? |
I like this theory, but my setup has the same version of libvirt (Fedora 38 has libvirt 9.0.0), and the virsh client version inside the flatpak reports 9.0.0 also. |
I created a crazy workaround to continue to use the Create button. Set up this override.
Then I use the GTK UI debugger to change the |
I think I fixed it for me. I personally set the environment variable
|
As already mentioned in https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/1001#note_1778741 the problem might be that the flatpak inherits the > export LIBVIRT_DEFAULT_URI=qemu:///system
> flatpak run --command=virsh org.gnome.Boxes uri
error: failed to connect to the hypervisor
error: Failed to connect socket to '/app/var/run/libvirt/virtqemud-sock': No such file or directory
>
> unset LIBVIRT_DEFAULT_DIR
>flatpak run --command=virsh org.gnome.Boxes uri
qemu:///session
> flatpak run org.gnome.Boxes --checks
(gnome-boxes:2): Boxes-WARNING **: 10:20:37.552: util-app.vala:422: Failed to execute child process ?restorecon? (No such file or directory)
• 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: no
Report bugs to <http://gitlab.gnome.org/gnome/gnome-boxes/issues>.
Boxes home page: <https://wiki.gnome.org/Apps/Boxes>. The Problem araises especially on Ubuntu Systems as canonical seems to explicitly set this environment variable to #!/bin/sh
# libvirt-uri.sh - Automatically switch default libvirt URI for user
# Copyright (C) 2015 Canonical Ltd.
#
# Authors: Stefan Bader <stefan.bader@canonical.com>
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, version 3 of the License.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
LIBVIRT_DEFAULT_URI="qemu:///system"
if [ -f /proc/xen/capabilities ]; then
if [ "$(cat /proc/xen/capabilities)" = "control_d" ]; then
LIBVIRT_DEFAULT_URI="xen:///"
fi
fi
export LIBVIRT_DEFAULT_URI If I explicitly overwrite the environment variable in the flatpak (setting it to |
Steps to reproduce:
flatpak install flathub org.gnome.Boxes
flatpak run org.gnome.Boxes
Expected results - VM is created and runs well.
Actual results - unable to create VM, terminal shows the following text:
Note: I can run both VirtualBox 6.1 and QEMU/KVM on this machine with Intel CPU.
The text was updated successfully, but these errors were encountered: