On 09.06.2013 11:43, Gleb Natapov wrote: > On Thu, Jun 06, 2013 at 02:10:39PM +0200, Stefan Pietsch wrote: >> On 06.06.2013 13:40, Gleb Natapov wrote: >>> On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote: >> >>>> I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae). >>>> >>>> The machine hangs after "Enabling APIC mode: Flat. Using 1 I/O APICs". >>> OK, since it looks like it hangs during timer initialization can you try >>> to disable kvmclock? Add -cpu qemu64,-kvmclock to your command line. >>> Also can you provide the output of "cat /proc/cpuinfo" on your host? And >>> complete serial output before hang. >> >> >> command line: >> qemu-system-i386 -machine accel=kvm -m 512 -cpu qemu64,-kvmclock -cdrom >> grml32-full_2013.02.iso -serial file:ttyS0.log >> >> >> ttyS0.log: >> ########## >> > > Nothing out of ordinary here. Since you can reproduce the hang and I > cannot, can you try and bisect it? Also can trace kvm during the hang > http://www.linux-kvm.org/page/Tracing? Start the trace as close to hang > as possible and stop it as quick after it as possible too to make trace > file smaller. git bisect tells me: 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit This is my bisect log: git bisect start git bisect bad 9626357371b519f2b955fef399647181034a77fe git bisect good ef4e359d9b9e2dc022f79840fd207796b524a893 git bisect good b5c78e04dd061b776978dad61dd85357081147b0 git bisect good 9e2d59ad580d590134285f361a0e80f0e98c0207 git bisect bad 69086a78bdc973ec0b722be790b146e84ba8a8c4 git bisect good 9ecf9b085a0926e07c78c08a07296bbfd1c37d07 git bisect bad 21fbd5809ad126b949206d78e0a0e07ec872ea11 git bisect bad 79fd50c67f91136add9726fb7719b57a66c6f763 git bisect good 66cdd0ceaf65a18996f561b770eedde1d123b019 -- 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
