[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] domu hangs?

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Wed, 08 Sep 2010 00:40:01 +0400
  • Delivery-date: Tue, 07 Sep 2010 14:03:33 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=FUURWKgVW9Yc4YSsHseqTdgCIZWyUTWrTgN2aDYC4EBzRx6Xa8VBTR9OIi67/D/YYf efAkay38rDDfRwfEmn6tOWMc2TAJTxDmfmTeyLJ9GcOTorxtuNr5ZDtbxwgnKVsBHkYU +b7s5QSDLVYWCgpm/qqMpoHySUOQtMY9PK4qw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Check memory usage. Some kernels for domU have bug with incorrect free
memory reporting. In this case in OOM situation kernel become mad and
killing every process and start to panic. And oom happens not at very
end of memory, but much early. 

Just try to disable swap in VM and 'eat' memory. I usually use
interactive python with constructions:
a=" "*1024*1024*256
b=" "*1024*1024*128
c=" "*1024*1024*64, etc... Until OOM happens. If python killed - kernel
sane. If Something Horrible Happens - buggy kernel. 

F.e. debian xen-686 kernel is buggy, I right now takling with
maintainers. Gentoo/SUSE kernel is fine with memory but have some issues
with wallclock.

Ð ÐÑÑ, 07/09/2010 Ð 15:28 -0500, John McMonagle ÐÐÑÐÑ:
> I have domu hanging on 3 different pv domus.
> All are dom0 and domu with Debian lenny.
> It happens randomly roughly once a month.
> There are no errors in the logs.
> Can not ping domu.
> xm console comes up but is unresponsive.
> Have tried watch watchdog with softdog bit it does not help.
> xm shutdown does not work.
> Have to restart with xm destroy, xm create.
> All have on_crash    = 'restart'  set.
> System1
> amd64 
> dom0 64bit  xen   xen 3.4.2
> domu  kernel 2.6.26-2-xen-amd64
> System 2
> intel  64 bit
> dom0 64bit  xen   xen 3.4.2
> domu  kernel 2.6.26-2-xen-amd64
> System3 ( This system had some random hangs before going to xen so it could 
> be 
> hardware)
> intel 32 bit
> dom0  2.6.26-2-xen-686 xen 3.2-1
> domu  2.6.26-2-xen-686
> While I'd like to fix it from hanging why doesn't xen restart it?
> I remember the on_crash    = 'restart' working fine in the past.
> What does on_crash look for?
> Any ideas?
> John
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.