<!-- This is the upstream QEMU issue tracker. If you are able to, it will greatly facilitate bug triage if you attempt to reproduce the problem with the latest qemu.git master built from source. See https://www.qemu.org/download/#source for instructions on how to do this. QEMU generally supports the last two releases advertised on https://www.qemu.org/. Problems with distro-packaged versions of QEMU older than this should be reported to the distribution instead. See https://www.qemu.org/contribute/report-a-bug/ for additional guidance. If this is a security issue, please consult https://www.qemu.org/contribute/security-process/ --> ## Host environment - Operating system: macOS Monterey - OS/kernel version: `Darwin MB-<redacted> 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000 arm64 arm Darwin` - Architecture: aarch64 - QEMU flavor: qemu-system-aarch64 - QEMU version: 7.1.0 - QEMU command line: <!-- Give the smallest, complete command line that exhibits the problem. If you are using libvirt, virsh, or vmm, you can likely find the QEMU command line arguments in /var/log/libvirt/qemu/$GUEST.log. --> ``` qemu-system-aarch64 -machine virt,highmem=off -display spice-app ``` ## Emulated/Virtualized environment (Not relevant) ## Description of problem <!-- Describe the problem, including any error/crash messages seen. --> ``` qemu-system-aarch64: info: Launching display with URI: spice+unix:///tmp/.U96NU1/spice.sock qemu-system-aarch64: warning: GLib-GIO: No default handler found for url scheme 'spice+unix'. qemu-system-aarch64: warning: GLib-GIO: No default handler found for url scheme 'spice+unix'. qemu-system-aarch64: Failed to launch spice+unix:///tmp/.U96NU1/spice.sock URI: Operation not supported qemu-system-aarch64: You need a capable Spice client, such as virt-viewer 8.0 ``` ``` $ virt-viewer --version virt-viewer version 11.0 ``` ## Steps to reproduce 1. Have virt-viewer in $PATH 2. Run command above 3. Observe error above ## Additional information <!-- Attach logs, stack traces, screenshots, etc. Compress the files if necessary. If using libvirt, libvirt logs and XML domain information may be relevant. --> <!-- The line below ensures that proper tags are added to the issue. Please do not remove it. -->