Hi, >From trace messages, it seemed no interrupts for guest. I also tried sysrq, but it didn't work. I doubt that kvm-qemu entered some infinite loop. Thanks, Paul On Mon, Aug 22, 2011 at 8:10 PM, Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote: > On Mon, Aug 22, 2011 at 10:37 AM, Paul <flypen@xxxxxxxxx> wrote: >> Hi, >> I found the clock of guest OS has been changed. For example, today was Aug >> 22, but I found the time of guest was Mar 22 from the VNC desktop. The clock >> source of guest was kvm-clock. Was it related to KVM clock bug? How about it >> if I changed the clock to tsc? > > If the guest is using 100% CPU but the kernel is still responsive at > some level you can use SysRq to gather information: > http://en.wikipedia.org/wiki/Magic_SysRq_key > > Especially Alt+SysRQ+t is interesting because it prints the current > tasks to the console. > > If you are able to get interactive access again then top(1) would be > interesting. > > Stefan > -- 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
