Sorry about the confusion, I don't have any domU guest running...
My grub menu.lst is,
kernel /boot/xen.gz watchdog=0 dom0_mem=1024M lowmem_emergency_pool=16M crashkernel=128M@32M nmi=dom0
module /boot/vmlinuz-2.6.27.42-0.1.1.xs5.6.0.44.111158xen ro ramdisk_size=250000 nmi_watchdog=0 xencons=off console=rcons0
module /boot/initrd-5.6.0-31188p.img
xen.gz is 64 bit one, while dom0 kernel is 32bit...
I am using echo c > /proc/sysrq-trigger to generate the kernel dump.
When I tried to open the kernel dump,
[debugger@crash HV_crash]$ crash32 vmlinux-2.6.27 vmcore-2010-09-02-22-30-38
crash32 5.0.3
……………….
This program has absolutely no warranty. Enter "help warranty" for details.
WARNING: machine type mismatch:
crash utility: X86
vmcore-2010-09-02-22-30-38: X86_64
crash32: vmcore-2010-09-02-22-30-38: not a supported file format
[debugger@crash HV_crash]$ crash64 vmlinux-2.6.27 vmcore-2010-09-02-22-30-38
crash64 5.0.3
………………….
WARNING: machine type mismatch:
crash utility: X86_64
vmlinux-2.6.27: X86
crash64: vmlinux-2.6.27: not a supported file format
Can you explain again what your setup is? I don't understand what
----- "Feng LI" <funglee@gmail.com> wrote:
> Hey you all,
>
> I am a kind of new to xen kernel dump analysis. Right now I have a
> fishy problem. I have generated vmcore dump from dom0 which is 32 bit
> PAE linux kernel running over 64 bit XEN kernel.
>
> BUT, I have diverticulitis to open the vmcore file. If I open it with
> crash32, crash32 would complain that vmcore is 64 bit image, while
> crash64 would complain dom0 kernel image is 32 bit.
>
> Could any body solve my problem ?
> Thanks in advance for any help and suggestions.
you mean when you say that you "have generated vmcore dump from dom0
which is 32 bit PAE linux kernel running over 64 bit XEN kernel".What crashed -- the 64-bit dom0 kernel or the 32-bit domU guest kernel?
Dave
>
> Yours
> Kevin F LI
--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility