On 11 Dec 2009, at 13:19, Daniel P. Berrange wrote: > On Wed, Dec 09, 2009 at 01:10:18PM -0800, Andrew Farmer wrote: >> Right now, if an incoming migrate through exec fails, the qemu process >> will end up chewing CPU indefinitely - it looks like it closes the >> migration FD but doesn't remove its IO handler properly. An easy way >> to reproduce this is to try launching with -incoming exec:/bin/false. >> This is obviously useless, but illustrates the issue handily. > > I've hit this in real life too, with restore from a file containing > the saved state which had got corrupted/truncated. I only discovered > the failure when I wondered by QEMU was chewing 100% cpu.
Hrm... actually, if this also happens on state restore, the problem might not be in migration-exec at all (or there might be multiple bugs with similar symptoms), as the fix I identified was specific to exec failures.
