On Thu, Feb 10, Dave Anderson wrote: > > > ----- Original Message ----- > > Hello, > > > > 'xm dump-core -L <domain>' generates a coredump of a Xen4 HVM guest, and > > crash is able to poke around in this coredump. > > Thanks for that. > > > > But: How can I use crash to debug the crash/kdump kernel itself? > > I did a 'echo c > /proc/sysrq-trigger' and want to look at the crash > > kernel, not the normal kernel. > > > > Olaf > > There is no facility for kdump'ing the secondary "kdump" kernel. 'xm dump-core' can appearently create the required core file while the kdump kernel runs. Just crash can appearently not "switch over". What should I modify in crash to let it work from a different "offset", in other words: the memory reserved for the kdump kernel? Olaf -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
