Hi, I was also experiencing this problem a lot for quite a long time (and for wide range of KVM versions..) I might be completely wrong as I'm not sure if it was really the reason, but i THINK it disappeared when I started to use fully preemptible kernel on host.. You might want to try it... BR nik On Sun, Mar 29, 2009 at 07:51:21AM +0000, Gerrit Slomma wrote: > Robert Wimmer <r.wimmer <at> tomorrow-focus.de> writes: > > > > > Hi, > > > > does anyone know how to solve the problem > > with "BUG: soft lockup - CPU#0 stuck for ..."? > > Today I got the messages below during compilation > > of the kernel modules in a guest. Using kvm84 and Kernel 2.6.29 > > as host kernel and 2.6.28 as guest kernel during the > > hangup of the guest neither ssh or ping was possible. > > After about 2 minutes the guest was reachable again > > and I saw the messages below with "dmesg". > > > > Maybe it is related with my prev. anserwed posting: > > http://article.gmane.org/gmane.comp.emulators.kvm.devel/29677 > > > > Thanks! > > Robert > > > > BUG: soft lockup - CPU#0 stuck for 61s! > > (...) > > Hello > > Do you use x86_64 or i686? > Look at my post here http://article.gmane.org/gmane.comp.emulators.kvm.devel/29833 > And my Bug-report here https://bugzilla.redhat.com/show_bug.cgi?id=492688. > I do not have the problems while running but after migrating. Problems with > stuck CPUs vanish if i686 for the host is used - but i am testing further. > > -- > 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 > -- ------------------------------------- Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@xxxxxxxxxxx ------------------------------------- -- 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
