3:27 p.m.
----- "Feng LI" <funglee(a)gmail.com> wrote:
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
Well, for starters, the crash utility must match the vmlinux file type,
i.e., you should be using the 32-bit version.
What is the output of:
# readelf -a vmcore-010-09-02-22-30-38
Dave
[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
3:32 p.m.
New subject: How to open 32 bit dom0 kdump....
Malparidoo no quiero que me mandes mas mensajes
Sent from my BlackBerry® wireless device
-----Original Message-----
From: Dave Anderson <anderson(a)redhat.com>
Sender: crash-utility-bounces(a)redhat.com
Date: Fri, 10 Sep 2010 16:27:02
To: Discussion list for crash utility usage,maintenance and
development<crash-utility(a)redhat.com>
Reply-To: "Discussion list for crash utility usage,
maintenance and development" <crash-utility(a)redhat.com>
Subject: Re: [Crash-utility] How to open 32 bit dom0 kdump....
----- "Feng LI" <funglee(a)gmail.com> wrote:
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
Well, for starters, the crash utility must match the vmlinux file type,
i.e., you should be using the 32-bit version.
What is the output of:
# readelf -a vmcore-010-09-02-22-30-38
Dave
[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
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
3:48 p.m.
New subject: How to open 32 bit dom0 kdump....
Thanks Dave.
I attached the output of elfread -a with this email...
Yours
Kevin F Li
4:03 p.m.
New subject: 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
8:15 p.m.
New subject: How to open 32 bit dom0 kdump....
Thanks Dave,
I had tried another combination: 32 bit Xen kernel with 32 bit Dom0 kernel,
but I have the similar issue. The vmcore file is still in 64 bit format.
(Our system has a large memory configuration 8GB-192GB), Is there any way I
can generate elf32 vmcore file ?
Thanks.
On Fri, Sep 10, 2010 at 5:03 PM, Dave Anderson <anderson(a)redhat.com> wrote:
----- "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
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
5041
days inactive
5043
days old
devel@lists.crash-utility.osci.io
4 comments
3 participants
participants (3)
-
antoniojavier09＠hotmail.com -
Dave Anderson -
LI, Feng