| Summary: | qemu command is often locked recently because tap0 still exists after successfully shutdown | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | liping Ke <liping.ke> |
| Component: | core | Assignee: | Scott Garman <scott.a.garman> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | dongxiao.xu, jessica.zhang, kevin.tian, lianhao.lu, meta.mr.watcher, meta.watcher, sgw |
| 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-20 19:57:28 UTC
fall into general bucket as qemu scripts consolidation and clean up, one more use case to test against manually kill the qemu process by "kill pid" can solve the problem. This bug is similar as BUG 294. O, kill pid does not work well. I kill all qemu related, still does not work. Since I can't pulldown tap0... The ideal behavior should be we have a tap dev pool, if user quit qemu, the associated tap device should be freed and next time a new qemu is running, it'll try to associate with the next available tap device if non available, the qemu script will exit will errors no available tap device. So the key issue that Scott needs to work on is to cleanly disassociate qemu with tap when exit qemu. This was fixed in the refactoring leading up to commit 0f973ed66551cdd1112ee9df42df5603835b8384. poky-qemu is now the only script for running qemu instances. Verified 2010-12-13 |