I've long used the patter of performing builds on a powerful headless build machine, then copying artefacts to my laptop in order to test them with runqemu. Unfortunately with the new runqemu this is broken and I can't just `runqemu /path/to/kernel /path/to/image` as I used to. Even if I copy the extra *.qemuboot.conf artefact I can't simply pass that to runqemu, I have to edit the configuration file to change the hardcoded paths from subdirectories of TMPDIR on the buildhost to the relevant paths on my laptop. We should support running images on machines other than the build host more easily, this could be either a) writing TMPDIR to the conf file and creating other paths relative to that b) massaging paths to be relative to the .conf file when a conf file is loaded We also need to make sure the new runqemu is fully documented so that any surprises are covered in the migration guide.
I have some lightly tested changes locally to resolve this. Will test further, clean up and submit on Monday.
Hi Joshua: Did you try something like: $ cp tmp/deploy/images/qemux86/ /tmp/mymachine -r $ runqemu /tmp/mymachine/ It works well for me.
Patches submitted: http://lists.openembedded.org/pipermail/openembedded-core/2016-September/126162.html
Fixed in OE-Core/Poky master.