Thanks, I managed to reproduce it and I'll send a patch to fix it soon. The reason for autotest thinking qemu wasn't alive was that apparently it takes time for /proc/$PID/cmdline to reflect the real command used to start the process, and I wrongly assumed it was instantaneous.
----- Original Message ----- From: "Gerd Hoffmann" <[email protected]> To: "Michael Goldish" <[email protected]> Cc: "KVM list" <[email protected]> Sent: Wednesday, August 5, 2009 4:21:54 PM (GMT+0200) Auto-Detected Subject: Re: [autotest] vm creation fails (not) On 08/05/09 15:12, Michael Goldish wrote: > Thanks! > I think I know exactly where it's hanging (get_status()) but I'm not > sure why. It hangs there because autotest thinks qemu didn't start. It did though. > Are you using Python 2.6? Yes (Fedora11). > What's the commit ID of the latest commit in > your autotest tree? commit 957e435541f27bb3b388a281ac13949288f75ad5 Author: mbligh <mbl...@592f7852-d20e-0410-864c-8624ca9c26a4> Date: Wed Jul 29 14:34:30 2009 +0000 cheers, Gerd -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
