On 06/07/2012 10:14 PM, Johannes Bauer wrote: > On 07.06.2012 19:25, Avi Kivity wrote: > >>> Note that "c" does NOT cause the VM to resume, only "info registers" >>> does. dmesg shows nothing out of the ordinary. >> >> I'm guessing this is 5152902652. Try bumping 'unsigned count = 130' (by >> adding zeros at the end, don't bother with anything less). If you >> increase it too much qemu may hang; but kill -9 should unfreeze it. > > Doesn't seem to be right -- still got the same problem. I first bumped > it up to 1300 and inserted debugging output to see how many cycles are > actually spent in the loop. It enters the emulation mode so frequently > (and leaves it again) that the dmesg buffer ran over (128kB). So I > changed the debugging to give me the lowest cycle count that it ever has > after the loop: > > handle_invalid_guest_state: emulation left, new low count 1295 > handle_invalid_guest_state: emulation left, new low count 1292 > handle_invalid_guest_state: emulation left, new low count 1291 > handle_invalid_guest_state: emulation left, new low count 1245 > > Which means that it spends a maximum of 55 cycles in the loop (well > below the original 130 even). So my change had no effect. Any other > ideas maybe? > Looks like we weren't dealing with interrupts correctly. I pushed some patches, please pull again and retry. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
