[Pkg-xen-devel] Bug#573210: Bug#573210: Bug#573210: xen-hypervisor-3.2-1-amd64: Xen domU sometimes hogs CPU and doesn't respond
pasik at iki.fi
Thu Mar 11 21:43:23 UTC 2010
On Thu, Mar 11, 2010 at 11:21:28PM +0200, Pasi Kärkkäinen wrote:
> On Tue, Mar 09, 2010 at 08:18:54PM +0100, Ondrej Kunc wrote:
> > Package: xen-hypervisor-3.2-1-amd64
> > Version: 3.2.1-2
> > Severity: normal
> > *** Please type your report below this line ***
> > Hi,
> > Recently I've experienced some crashes of Xen domU (also debian Lenny,
> > running same kernel as dom0 (linux-image-2.6.26-xen-amd64)).
> > At xm top that domain appears as running, but hogs all CPUs, because
> > this problem has appeared on two identic servers (Supermicro X7SBi, QC
> > Xeon, 8G DDR II). I think that problem cannot be in hardware. We were
> > running this configuration on some other servers with core2 duo
> > processor (only dualcore) and there this problem never appeared. I've
> > saved a core-dump of affected domU, but it's really big(1,1GB), so I'll
> > not attach it to bugreport, but it is available for debugging.
> > Thanks for potential interest in debugging.
> It's this problem:
> I tried getting debug info (stack traces) of the crashed guest here:
> but it'd need more investigations and actual debugging..
Btw the workaround should be to use only a single vcpu per each guest..
Having multiple vcpus for the domU running the 2.6.26-2-xen kernel causes problems.
More information about the Pkg-xen-devel