12125 2017-09-25 14:46:57 +0000 runqemu-gen-tapdevs not working when using directly from build-dir 2018-01-29 20:43:34 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.4 x86 Multiple RESOLVED WONTFIX Backport 2.3.3? Medium normal 2.5 1 jose.perez.carranza stephano akuster brian.avery randy.macleod ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 77099 0 jose.perez.carranza 2017-09-25 14:46:57 +0000 script runqemu-gen-tapdevs is not working when is used from build directory. Note: Is working correctly when used from scripts directory commit b32174e58e89119e3ca2315030629a6580ccbd52 STEPS TO REPRODUCE: 1. clone poky 2. $source oe-init-build-env 3. Under build directory run $ sudo ./../scripts/runqemu-gen-tapdevs 1000 1000 4 tmp/sysroots-components/x86_64/qemu-helper-native/usr/bin EXPECTED RESULT: script works correctly and TAP devices are generated ACTUAL RESULT: sudo: runqemu-gen-tapdevs: command not found 77198 1 jose.perez.carranza 2017-09-28 14:28:50 +0000 Correction to step 3 3. Under build directory run $ sudo runqemu-gen-tapdevs 1000 1000 4 tmp/sysroots-components/x86_64/qemu-helper-native/usr/bin Note: below command works correctly sudo ./../scripts/runqemu-gen-tapdevs 1000 1000 4 tmp/sysroots-components/x86_64/qemu-helper-native/usr/bin 77209 2 brian.avery 2017-09-28 20:12:35 +0000 This is because the PATH on most modern systems reset for security reasons when you sudo. So, we probably should close this bug and open another bug for documentation to make explicit that you should run it as sudo <absolute path> or <relative path> but should NOT rely on the PATH correctly resolving. We may also want to add in the documentation bug that for this tool to work, the user needs to have built qemu-helper-native or else the tunctl command (which is what this uses) will not be available. 79266 3 stephano 2018-01-29 20:43:34 +0000 Replaced by Bug 12517.