On Thu, Aug 16, 2012 at 2:22 PM, Mark van Dijk
<lists+xen@internecto.net>wrote:
> On Thu, 16 Aug 2012 12:58:51 +0530
> Francis Pereira <francispereira@7terminals.com> wrote:
>
> > I had a server simply "freeze" yesterday - no response from
dom0 or
> > domU. There is nothing suspicious (out of the ordinary)
> > in /var/log/kern, xcp-xapi and syslog in dom0, domU and physical
> > server'' logs. Looks like the running system simply hung and a
reboot
> > was required. Can someone point me to documentation or tips on how to
> > debug such lockups in Xen environment.
>
> Hi Francis, maybe these pages can help:
>
> http://wiki.xen.org/wiki/Xen_Serial_Console
> and
>
>
http://wiki.xensource.com/xenwiki/XenParavirtOps.html#head-9fb34d1cf597800d371b844568797d4db8587dce
>
> Kind regards,
> Mark
>
>
Hi Mark,
A serial console is not very scalable especially if random servers
hang/reboot every now and them. I want to have a process in place
where every-time a dom0 or Xen kernel freezes - a core dump
is automatically generated. I have been reading about kdump and kexec,
while its fairly straight forward for a normal Linux kernel that is booted
on bare hardware, I don''t understand how to set it up correctly with
Xen
and dom0. Google searches for kdump and Xen provide results for Xen 3.x.
Some results seem to suggest that there is a kdump port for Xen. Can
someone point me to latest documentation on kdump and Xen.
XenServer appears to use kdump ( I can see crashkernel= in the kernel line)
to generate a crash dump which can be used by support to debug but I am not
sure how they have put it all together
~Francis
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users