| Summary: | runqemu command not found after source /opt/poky/environment-setup-armv5teXXX | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | liping Ke <liping.ke> |
| Component: | kernel-tooling | Assignee: | Scott Garman <scott.a.garman> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, kevin.tian, scott.a.garman, sgw, yp.watcher |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
liping Ke
2010-09-14 01:27:43 UTC
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 |