|Subject:||[Qemu-devel] [Question] Different test result about guest softlock|
|Date:||Mon, 25 May 2015 17:03:04 +0800|
Hi, all :
I have done some test about guest softlock panic by force the qemu main thread stuck in a timer callback function. After several minutes, let the qemu resume.
I append the "softlockup_panic=1" to the kernel cmdline and check the /proc/sys/kernel/softlockup_panic.
dist kernel clock source result
redhat 6.5 2.6.32 kvm-clock no panic
redhat 5.5 2.6.18 jiffies panic
centos 6.5 2.6.32 kvm-clock no panic
centos 5.5 2.6.18 jiffies/kvm-clock no panic
fedora 13 2.6.33 kvm-clock no panic
I am curious why redhat 5.5 have the different result ? Anything I missed?
Should the guest panic because of the stuck in qemu main thread?
|[Prev in Thread]||Current Thread||[Next in Thread]|