I've just submitted a "test-runner: Allow to use host CPU on demand" patch which should fix that. Unfortunately, I'm not able to test it right now, but I think that it will work. I've tested it like that (on my RPi) and it seems to be OK: $ tools/test-runner -k bzImage -H -q /usr/bin/echo -a Using QEMU binary /usr/bin/echo Using kernel image bzImage -nodefaults -no-user-config -monitor none -display none -machine type=q35,accel=kvm:tcg -m 256M -net none -no-reboot -fsdev local,id=fsdev-root,path=/,readonly=on,security_model=none,multidevs=remap -device virtio-9p-pci,fsdev=fsdev-root,mount_tag=/dev/root -chardev stdio,id=con,mux=on -serial chardev:con -cpu host -kernel bzImage -append console=ttyS0,115200n8 earlyprintk=serial no_hash_pointers=1 rootfstype=9p rootflags=trans=virtio,version=9p2000.u acpi=off pci=noacpi noapic quiet ro init=/home/pi/bluez/build/./tools/test-runner TESTHOME=/home/pi/bluez/build TESTDBUS=0 TESTDAEMON=0 TESTDBUSSESSION=0 XDG_RUNTIME_DIR=/run/user/0 TESTMONITOR=0 TESTEMULATOR=0 TESTDEVS=0 TESTAUTO=1 TESTAUDIO='' TESTARGS='(null)' I've just noticed a "TESTARGS='(null)'"... However, maybe that's intended. Anyway passing NULL to snprintf is a risky business. Regards, Arek
