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


Re: [Xen-devel] domU crashing, trying to determine why

On Mon, 2011-01-03 at 16:40 +0000, Konrad Rzeszutek Wilk wrote:
> > > I've got this setup:
> > > 
> > > vcpus=2
> > > cpus=[1,3]
> Is there anything in the Xen hypervisor ring buffer?

Equally was there anything on the guest console? If it is dying before
you can look then you can enable logging via XENCONSOLED_TRACE=guest
in /etc/sysconfig/xencommons or /etc/default/xencommons (depending on
distro). Logs show up in /var/log/xen/guest/

If the guest is still running but deadlocked or similar then it might be
worth sending a few SysRQs to it. To do this press Ctrl-O on the guest
console and press one of the magic letters, 'h' will give help.
't' (tasks) would be a useful start as would 'p' (processor state).

It might be worth compiling your guest kernel with lockdep support and
seeing if it complains about anything.

Also, I notice you seem to be running the Debian Lenny classic-Xen
forward port. Are you running the most recent version of that kernel?
Unfortunately there is not much developer interest in these classic-Xen
forwards ports these days.

You could also try the -686-bigmem kernel flavour from Lenny which is a
PVops enabled kernel, or perhaps a Squeeze kernel from backports.org
(either -686-bigmem or -xen-686, both are pvops kernels). If your
problem persists with these then there is more chance of it getting
fixed than with the Lenny -xen-686 flavour.


>  You might need to enable the 
> full logging of the guest and dom0 to get anything there.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list