Ben: Yup, I can write perfectly on your generated images, so it&#39;s not a problem with qemu. I thought the correct boot option would be 5, but then I&#39;ll use 9queen and then sooner or later I&#39;ll see if I can understand everything else is there, Plan9 is relatively complex in its namespace stuff (coming from a mostly Linux/Mac OS background) and ANTS is... complex, although your use cases look very interesting &amp; appealing :). And also, if it works, why break it :)? I have a working image!<div>

<br></div><div>Kurt: My system is an old Macbook (Early 2008 IIRC, underpowered by today&#39;s standards but it&#39;s relatively okay) but qemu in general works relatively well, and once an image works and is booted works perfectly. So I&#39;m guessing it&#39;s some problem with my qemu build (1.4.0) tied with some way Plan9 tries to write to disk. Or not, it&#39;s quite puzzling.</div>

<div><br></div><div>Thanks!</div><div><br></div><div>Ruben<br><br><div class="gmail_quote">On Tue, Mar 12, 2013 at 5:15 PM, Kurt H Maier <span dir="ltr">&lt;<a href="mailto:khm-9@intma.in" target="_blank">khm-9@intma.in</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Mar 12, 2013 at 01:53:26PM +0100, Ruben Berenguel wrote:<br>
&gt;<br>
&gt; Hangs on copydist (waited ~20 minutes.)<br>
<br>
</div>I&#39;ve seen copydist take longer than this on underpowered or incorrectly<br>
configured systems.  The way it performs the copy is an unmitigated seek<br>
festival.  On one of my machines it took a little over an hour; this is<br>
why I&#39;m grateful for cinap&#39;s virtio driver, which cut that time in half.<br>
<span class="HOEnZb"><font color="#888888"><br>
khm<br>
<br>
</font></span></blockquote></div><br></div>