Bug#925621: virsh: error: internal error: Failed to probe QEMU binary with QMP:\n
On Wed, 27 Mar 2019, Thorsten Glaser wrote: > I cannot start any VM any more: > > tglase@tglase:~ $ virsh -c qemu:///system start Netboot > error: Failed to start domain Netboot > error: internal error: Failed to probe QEMU binary with QMP: I’ve just, after a reboot, seen something interesting in syslog, which indicates that newer libvirt MIGHT be starting the qemu processes as dæmons in the background, instead of just when the VMs are started. Is this true, and, if so, can it be disabled? My is a shell script looking like this: tglase@tglase:~ $ cat /usr/local/bin/qemu-in-chroot #!/bin/sh exec schroot -c sid-amd64 -u root -- qemu-system-x86_64 -enable-kvm "$@" The reason for this is that qemu:x32 cannot give the VMs enough virtual memory and that I need the amd64 binaries for that, but I don’t want to always use the amd64 binaries, so I have both, and amd64 only in chroot (plus the library dependencies are heavy enough to preclude installation of the amd64 M-A alternative on the main x32 system). bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg * **!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an. Besuchen Sie uns auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf Ihren Kontakt. *
Bug#925621: virsh: error: internal error: Failed to probe QEMU binary with QMP:\n
Package: libvirt-clients Version: 5.0.0-1 Severity: important I cannot start any VM any more: tglase@tglase:~ $ virsh -c qemu:///system start Netboot error: Failed to start domain Netboot error: internal error: Failed to probe QEMU binary with QMP: 1|tglase@tglase:~ $ sudo tail -4 /var/log/libvirt/libvirtd.log 2019-03-27 17:46:06.808+: 22362: error : virQEMUCapsNewForBinaryInternal:4681 : internal error: Failed to probe QEMU binary with QMP: 2019-03-27 17:46:06.821+: 22362: warning : virQEMUCapsLogProbeFailure:4628 : Failed to probe capabilities for /usr/bin/kvm: internal error: Failed to probe QEMU binary with QMP: 2019-03-27 17:49:44.508+: 22362: error : virQEMUCapsNewForBinaryInternal:4681 : internal error: Failed to probe QEMU binary with QMP: 2019-03-27 17:49:44.508+: 22362: warning : virQEMUCapsLogProbeFailure:4628 : Failed to probe capabilities for /usr/bin/kvm: internal error: Failed to probe QEMU binary with QMP: -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages libvirt-clients depends on: ii libacl1 2.2.53-4 ii libapparmor12.13.2-9 ii libaudit1 1:2.8.4-2 ii libavahi-client30.7-4+b1 ii libavahi-common30.7-4+b1 ii libc6 2.28-8 ii libcap-ng0 0.7.9-2 ii libcurl3-gnutls 7.64.0-2 ii libdbus-1-3 1.12.12-1 ii libdevmapper1.02.1 2:1.02.155-2 ii libgcc1 1:8.3.0-3 ii libgnutls30 3.6.6-3 ii libnl-3-200 3.4.0-1 ii libnl-route-3-200 3.4.0-1 ii libreadline77.0-5 ii libsasl2-2 2.1.27+dfsg-1 ii libselinux1 2.8-1+b1 ii libssh2-1 1.8.0-2 ii libvirt05.0.0-1 ii libxml2 2.9.4+dfsg1-7+b3tarent1 ii libyajl22.1.0-3 ii sensible-utils 0.0.12 libvirt-clients recommends no packages. Versions of packages libvirt-clients suggests: ii libvirt-daemon 5.0.0-1 -- no debconf information
