-.qemuboot.conf 39- No Such File Or Directory ((hot))
ls -la tmp/deploy/images/<your-machine>/*.qemuboot.conf
Then run runqemu again. If it works, you have confirmed a path resolution bug in your version of runqemu .
-.qemuboot.conf 39- no such file or directory Context: Likely occurring during a Yocto/OpenEmbedded build or QEMU run, when the system expects a .qemuboot.conf file but cannot find it.
ls tmp/deploy/images/<your-machine>/*.qemuboot.conf -.qemuboot.conf 39- no such file or directory
bitbake -c cleanall <your-image> bitbake <your-image>
Looking for .qemuboot.conf in: -
A normal filename would be like core-image-minimal-qemuarm64.qemuboot.conf . A filename like -.qemuboot.conf suggests that a variable used to construct the filename was or unset , leaving only the dash and the extension. ls -la tmp/deploy/images/<your-machine>/*
Do copy runqemu to a different directory and run it from there.
You might notice the strange hyphen prefix in the error log ( -.qemuboot.conf ). This is often a result of string manipulation within the runqemu script. If the script attempts to construct the filename based on a machine variable that is empty or unset, it may produce a malformed filename starting with a hyphen. This suggests that the environment variables defining your target machine are not being passed correctly to the execution script.
Alternatively, you can force regeneration of just the deployment artifacts: ls tmp/deploy/images/<your-machine>/*
Run runqemu with debug output to see exactly what it is doing:
:If the file is missing, try cleaning and rebuilding the specific image: bitbake -c clean bitbake .
: Some Board Support Packages (BSPs) do not support running under QEMU and thus do not generate this file by default. Path Mismatch script expects the file in tmp/deploy/images/ / - .qemuboot.conf . If you have manually moved images or changed your DEPLOY_DIR , the script may fail to find it. Migration to JSON : In newer versions of OpenEmbedded-Core, qemuboot.conf has been replaced by qemuboot.json for better compatibility with modern tools. The Yocto Project How to Fix or Workaround Re-run the Image Build : Ensure your build is successful by running bitbake . Check the logs for any failures in the Verify the Deploy Directory : Manually check your deploy directory (e.g., tmp/deploy/images/ / ) to see if any *.qemuboot.conf *.qemuboot.json files exist. Specify the File Manually