<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>344</bug_id>
          
          <creation_ts>2010-09-20 19:57:28 +0000</creation_ts>
          <short_desc>qemu command is often locked recently because tap0 still exists after successfully shutdown</short_desc>
          <delta_ts>2010-12-28 23:24:01 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>0.9</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>0.9 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="liping Ke">liping.ke</reporter>
          <assigned_to name="Scott Garman">scott.a.garman</assigned_to>
          <cc>dongxiao.xu</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>kevin.tian</cc>
    
    <cc>lianhao.lu</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          <cf_verified>Program Management</cf_verified>
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>9917</commentid>
    <comment_count>0</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-09-20 19:57:28 +0000</bug_when>
    <thetext>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&apos;s very annoying... Since I have to restart the machine to get a cleaner environment. Anybody know how to solve this problem?

Thanks &amp; Regards,
criping</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9919</commentid>
    <comment_count>1</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2010-09-20 20:02:41 +0000</bug_when>
    <thetext>fall into general bucket as qemu scripts consolidation and clean up, one more use case to test against</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9920</commentid>
    <comment_count>2</comment_count>
    <who name="Dongxiao Xu">dongxiao.xu</who>
    <bug_when>2010-09-20 20:03:29 +0000</bug_when>
    <thetext>manually kill the qemu process by &quot;kill pid&quot; can solve the problem. 

This bug is similar as BUG 294.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9921</commentid>
    <comment_count>3</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-09-20 20:06:30 +0000</bug_when>
    <thetext>
O, kill pid does not work well.
I kill all qemu related, still does not work. Since I can&apos;t pulldown tap0...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9922</commentid>
    <comment_count>4</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2010-09-20 20:08:31 +0000</bug_when>
    <thetext>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&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10208</commentid>
    <comment_count>5</comment_count>
    <who name="Scott Garman">scott.a.garman</who>
    <bug_when>2010-10-07 14:18:25 +0000</bug_when>
    <thetext>This was fixed in the refactoring leading up to commit 0f973ed66551cdd1112ee9df42df5603835b8384. poky-qemu is now the only script for running qemu instances.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11125</commentid>
    <comment_count>6</comment_count>
    <who name="Scott Garman">scott.a.garman</who>
    <bug_when>2010-12-13 08:39:59 +0000</bug_when>
    <thetext>Verified 2010-12-13</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>