This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: Lenny DomU crash!

Ferenc Wagner wrote:

 > I'm getting the same thing - DomU runs fine for weeks or months, but
 then our monitoring system tells us it's down. From the outside, it's
 'dead' - doesn't respond to pings or anything. From Dom0 we can
 connect to the console (xm console <guestname>) and get the last few
 pages of output - but there's nothing unusual logged (just a load of
 Shorewall log lines which is normal). The guest is absolutely dead to
 the console as well.

 xentop reports that teh guest is taking 100% cpu.

 All I can do is kill it and restart it.

 Almost all my guests are Debian Lenny, installed with debbootstrap and
 then cloned. Some have never done it (yet !), others have done it two
 or three times over the last few months.

 Dom0 runs 2.6.18-6-xen-686
 Guests run 2.6.18-5-xen-vserver-686 or 2.6.18-6-xen-686 - both have
 guests that have never crashed, both have guests that have.

See http://thread.gmane.org/gmane.comp.emulators.xen.devel/55056/ for
a workaround.  I also encountered this problem
however, my guest are running the stock Lenny kernel (2.6.26).

Hmm, I don't think it's that - my symptoms are different.

From the first link, I see that this event is characterised by an inability to start PV guests and existing guests showing state blocked. In my case, I can start a PV guest, and the stuck guest shows state running and consumes 100% cpu.

Also, if it were that, wouldn't I expect to see other guests on the same host lock up ?

Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>