Hi, Josh After source /opt/poky arm setup files, I found runqemu is not found any more. That means I must use poky-qemu instead. Is this an anticipated behavior? But after I source poky_tree/build-arm/tmp/environment-setup-armXXX set up script files, I found runqemu, but command runqemu qemuarm will report error. (Couldn't find image in /deploy/images), seems this is path error. If I source build script, I can runqemu qemuarm successfully. Seems runqemu, poky-qemu have messed-up behaviors combined with setup/build scripts. Could you help to clarify what's your anticipated behavior? Thanks a lot for your help! criping
Can you use poky-qemu successfully in both cases?
Hi, Richard, Yes, I can. So runqemu script could be discarded to external users? We all should use poky-qemu instead? criping
I think this fall into the general task for M4 to consolidate our poky-qemu script, adding scott to the cc list. There's another bug filed for that 295. Currently there're way too many scripts for qemu that get people confused and trapped. The ultimate goal based on my understanding and discussion with Scott is we'll eventually have one script called poky-qemu to bring up Qemu. In the mean time, please use poky-qemu if you want to bring up Qemu in none unfs mode, otherwise, use runqemu-unfs which is the only way to bring unfs qemu at the moment.
This has been fixed in the refactoring leading up to commit 0f973ed66551cdd1112ee9df42df5603835b8384. poky-qemu has replaced runqemu as Poky's QEMU control script.
The latest qemu script should be one and only one poky-qemu