Re: [Crash-utility] How to open 32 bit dom0 kdump....
----- "Feng LI" <funglee(a)gmail.com> wrote:
Thanks Dave.
I attached the output of elfread -a with this email...
Hmmm -- now that I think about it, it's seems that the crash
utility has never supported dom0 vmcores generated from this
type of Xen hypervisor/dom0 combination.
Red Hat kernel versions come with the xen.gz and vmlinuz files
packaged together, i.e., both 64-bit or both 32-bit:
# rpm -qpl kernel-xen-2.6.18-219.el5.x86_64.rpm
/boot/.vmlinuz-2.6.18-219.el5xen.hmac
/boot/System.map-2.6.18-219.el5xen
/boot/config-2.6.18-219.el5xen
/boot/symvers-2.6.18-219.el5xen.gz
/boot/vmlinuz-2.6.18-219.el5xen
/boot/xen-syms-2.6.18-219.el5
/boot/xen.gz-2.6.18-219.el5 <= 64-bit
...
# rpm -qpl kernel-xen-2.6.18-219.el5.i686.rpm
/boot/.vmlinuz-2.6.18-219.el5xen.hmac
/boot/System.map-2.6.18-219.el5xen
/boot/config-2.6.18-219.el5xen
/boot/symvers-2.6.18-219.el5xen.gz
/boot/vmlinuz-2.6.18-219.el5xen
/boot/xen-syms-2.6.18-219.el5
/boot/xen.gz-2.6.18-219.el5 <= 32-bit
...
So, it's highly unlikely that either internally to Red Hat,
or any of our customers, would ever run such a combination.
And I don't recall ever working with the crash utility to
support it.
I'm curious whether anybody on this list has ever done this?
After all these years of Xen existence, you would think that
somebody else would have bumped into this anomoly before...
Dave