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

Re: [Xen-users] debugging system crashes

Follow-up: I think this was an hardware issue.
I was passing through my VGA card and after a few days I started having video corruption issues at the same time of this. Now I have video corruption (snow, black lines, etc.) and this is definitively an hardware problem. I am hoping the new card will be as compatible as my FirePro
Thanks all

On Sat, Jan 21, 2012 at 9:52 AM, Florian Heigl <florian.heigl@xxxxxxxxx> wrote:
Hi Enzo,

2012/1/21 Enzo Lombardi <enzinol@xxxxxxxxx>:
> Hello all,
> I've experienced this issue a couple of times.
> Dom0 replies to pings, but ssh refuses. All DomU are unresponsive, some

so your kernel is still working, but i.e. disk access has been lost.

some steps you can go through:
1. /var/log/messages /var/log/*  (anything where your distro decides
to put relevant messages)
2. enable a serial console, and log in there (and make sure you stay
logged in). If you can still use it at the time of "ssh not working",
then debug as like on a normal unix system, but go sure to also view
xm dmesg output.
3. if everything goes unusable, disable vga screen blanking on the
main console to see the last console output, or run a serial console
4. after that enable sysrq using sysctl and look up how to trigger a
crash via the serial console. (if possible)


Xen-users mailing list



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