10211 2016-09-02 16:04:02 +0000 New runqemu makes it harder to use on hosts other than the build machine 2016-09-09 12:49:50 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.2 x86 Multiple RESOLVED FIXED Medium+ normal 2.2 M3 1 joshuagloe joshuagloe liezhi.yang ross.burton --- --- Yes (doc changes required) oldest_to_newest 65772 0 joshuagloe 2016-09-02 16:04:02 +0000 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. 65779 1 joshuagloe 2016-09-02 22:22:14 +0000 I have some lightly tested changes locally to resolve this. Will test further, clean up and submit on Monday. 65781 2 liezhi.yang 2016-09-03 02:44:33 +0000 Hi Joshua: Did you try something like: $ cp tmp/deploy/images/qemux86/ /tmp/mymachine -r $ runqemu /tmp/mymachine/ It works well for me. 65822 3 joshuagloe 2016-09-06 10:18:43 +0000 Patches submitted: http://lists.openembedded.org/pipermail/openembedded-core/2016-September/126162.html 65991 4 joshuagloe 2016-09-09 12:49:50 +0000 Fixed in OE-Core/Poky master.