After I shutdown a qemu (ppc, for example), everything is fine. But if I restart a new qemu, the command is locked. I checked that tap0 is still there. If I ctl+c, it will use another ipaddress and go on. But if I tried ty poky-qemu-ifdown tap0, it will say TUNSETIFF: Device or resource buzy. It's very annoying... Since I have to restart the machine to get a cleaner environment. Anybody know how to solve this problem? Thanks & Regards, criping
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