Comment 8 for bug 879710

Ouch. I replaced the code with the new lines and ran vmbuilder twice. "Unfortunately" everything worked fine this way and I couldn't reproduce the problem again (obviosuly I removed the run_cmd('sleep', '10') fix too).

I experienced something similar with another server, at first vmbuilder crashed but after making some other changes (like apt-get installing something else, totally unrelated) vmbuilder was able to complete its job and never saw the problem again in that server.

I'm wondering if this could be related to getting stuck in some hard disk sector but that doesn't make much sense. The other server I'm referring to is a 4-years-old Core 2 Duo laptop and my current server is a brand new Core i5 desktop, so hardware seems totally unrelated.

I'll let you know if I can reproduce the problem again, sorry I can't help more for now.