<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bisect on Chris J Arges</title><link>https://chrisarges.net/tags/bisect/</link><description>Recent content in Bisect on Chris J Arges</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 16 Dec 2013 14:39:00 -0800</lastBuildDate><atom:link href="https://chrisarges.net/tags/bisect/index.xml" rel="self" type="application/rss+xml"/><item><title>automatic bisection of qemu with console and monitor interaction</title><link>https://chrisarges.net/posts/2013-12-16-automatic-bisection-of-qemu-with/</link><pubDate>Mon, 16 Dec 2013 14:39:00 -0800</pubDate><guid>https://chrisarges.net/posts/2013-12-16-automatic-bisection-of-qemu-with/</guid><description>&lt;p&gt;I had some fun debugging a performance &lt;a href="http://pad.lv/1100843"&gt;issue&lt;/a&gt; after VM migration on v1.0.&#10;Because this was fixed in newer versions, a bisect was in order. Doing this&#10;manually becomes very tedious so writing some scripts to use &lt;code&gt;git bisect run&lt;/code&gt;&#10;really helps. Here I&amp;rsquo;ll document how I did this in case others find it useful&#10;when trying to bisect issues in qemu.&lt;/p&gt;&#10;&lt;p&gt;First step is getting the problem reproducible using the command line. In&#10;addition you will also need to output anything that be used to determine if the&#10;test case passes or fails using standard console output. This makes it easy to&#10;run the test case with expect. You will need to &lt;a href="https://help.ubuntu.com/community/SerialConsoleHowto"&gt;follow&lt;/a&gt; on how to setup your&#10;VM to use serial output.&lt;/p&gt;</description></item></channel></rss>