<?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>10829</bug_id>
          
          <creation_ts>2016-12-20 16:20:26 +0000</creation_ts>
          <short_desc>runqemu: Add python module</short_desc>
          <delta_ts>2023-06-22 15:21:12 +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>Scripts and Tools</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>OBSOLETE</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>Future</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Mariano Lopez">mariano.lopez</reporter>
          <assigned_to name="Unassigned">unassigned</assigned_to>
          <cc>benjamin.esquivel</cc>
    
    <cc>randy.macleod</cc>
    
    <cc>rebecca.swee.fun.chang</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>ross.burton</cc>
    
    <cc>sgw</cc>
    
    <cc>tim.orling</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>New (Never tested)</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>69232</commentid>
    <comment_count>0</comment_count>
    <who name="Mariano Lopez">mariano.lopez</who>
    <bug_when>2016-12-20 16:20:26 +0000</bug_when>
    <thetext>Now that runqemu was refactor to use python it would be nice to have a module that can be imported in other parts of the project. This would be beneficial specially for selftest and runtime testing. The current implementation has to run qemu using a shell, and because of that there are checks to be sure that qemu is killed after the parent process is killed or ends unexpectedly.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>69321</commentid>
    <comment_count>1</comment_count>
    <who name="Benjamin Esquivel">benjamin.esquivel</who>
    <bug_when>2016-12-22 16:09:26 +0000</bug_when>
    <thetext>Mariano, would you add these 2 things to the bug description:

1. source of the requirement (which effort or module requires it?)
2. benefits that are sought with this enhancement</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>69323</commentid>
    <comment_count>2</comment_count>
    <who name="Mariano Lopez">mariano.lopez</who>
    <bug_when>2016-12-22 16:33:34 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; Mariano, would you add these 2 things to the bug description:
&gt; 
&gt; 1. source of the requirement (which effort or module requires it?)
The main consumer that I see is the QemuRunner class in oeqa library, currently runqemu has to be called using a shell because of the command line parameters used in the script.

&gt; 2. benefits that are sought with this enhancement
In QemuRunner class we have some hacks to kill the shell that called runqemu, and the qemu-system process in case QemuRunner&apos;s process ends unexpectedly. I&apos;ve been working lately with QemuRunner and it seems qemu-system is not always killed when a bitbake worker (using testimage) is killed; I must admit that it happens sporadically, about 10% of the time.

So, the benefit here is to have call directly runqemu from python without using a shell, with this we would have better control of the qemu process avoiding hacks.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>71102</commentid>
    <comment_count>3</comment_count>
    <who name="Ed Bartosh">eduard.bartosh</who>
    <bug_when>2017-03-07 11:27:40 +0000</bug_when>
    <thetext>I don&apos;t think I&apos;ll have time to work on this in 2.3 time frame.
moving to 2.4, increasing estimate.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>90691</commentid>
    <comment_count>4</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-06-17 15:27:22 +0000</bug_when>
    <thetext>Still a good idea. Any volunteers?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95810</commentid>
    <comment_count>5</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2023-06-22 15:21:12 +0000</bug_when>
    <thetext>We&apos;ve had many changes in runqemu since this was written. Open a new defect if there are similar ERs you would like to see.
-- YP bug review.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>