I managed to reproduce this quite reliably so did some trials to find out how to improve things.
This is 64bit dom0 on Xen 3.3.0 (On Centos) on Dell 2940s The domU is a 32bit Hardy box with 1G ram. With all the available hardy Xen kernels, this soft lockup kept happening. I tried also tried "clocksource=jiffies". Then I tried the latest Intrepid kernels and the problem was solved. As I understand, the Intrepid kernel has the proper kernel.org upstream xen support (rather than the forward ported patch from 2.6.18 as is Hardy iirc). So whilst this solves the problem (for me), it's a pretty big change and isn't something I'd expect to see "backported" to Hardy. The new upstream Xen stuff changes the way block devices and the console are done, so you can't switch without some tweaks to your Xen configs (and guest OS config) but other than that it seemed to work fine with Hardy. Incidentally, I replaced this domU with a 64bit Hardy install, with the standard 64bit Hardy kernel, and that also solved the soft lockups. -- xen virtual Machines and Dom0 crashes with "BUG: soft lockup - CPU#0,CPU#1,CPU#2,CPU#3 stuck for 11s!" https://bugs.launchpad.net/bugs/259487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
