- Original Message -
>
>
>
> I can't run crash on the live system
>
> Vsles11-1:/usr/src/linux # crash -d8 vmlinux
>
>
> crash 5.0.1
> Copyright (C) 2002-2010 Red Hat, Inc.
> Copyright (C) 2004, 2005, 2006 IBM Corporation
> Copyright (C) 1999-2006 Hewlett-Packard Co
> Copyright (C)
I can't run crash on the live system
Vsles11-1:/usr/src/linux # crash -d8 vmlinux
crash 5.0.1
Copyright (C) 2002-2010 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006 Fujitsu Limited
Copyright (C) 2006,
- Original Message -
>
>
> It is wrong in last mail , correct as follow:
>
>
> xen and dom0 is x86_64
>
>
> when para x86_64 domU, problem happens
> when hvm 32bit domU , crash can work correctly.
Just for sanity's sake, log into the x86_64 domU, run crash
on the live system, and e
It is wrong in last mail , correct as follow:
xen and dom0 is x86_64
when
para
x86_64 domU, problem happens
when hvm 32bit domU , crash can work correctly.
From: duanshui...@hotmail.com
To: crash-utility@redhat.com
Date: Thu, 27 Oct 2011 14:18:11 +
Subject: Re: [Crash-util
running 64-bit Xen guests on a 32-bit dom0.
-》NO
xen and dom0 is x86_64
when domU is x86_64 , problem happens
when para 32bit domU , crash can work correctly.
> Date: Thu, 27 Oct 2011 09:45:00 -0400
> From: ander...@redhat.com
> To: crash-utility@redhat.com
> Subject: Re: [Cras
Ok, I can continue to compile a vmlinux for testing.
> Date: Thu, 27 Oct 2011 09:34:56 -0400
> From: ander...@redhat.com
> To: crash-utility@redhat.com
> Subject: Re: [Crash-utility] [help]crash can't anaylyse xen guest
> paravirtulized linux vmcore
>
>
>
> - Original Message -
On 27 October 2011 14:45, Dave Anderson wrote:
> Red Hat never supported running 64-bit Xen guests on a 32-bit
> dom0.
>
>
Yeah, it's just a bad idea. I ran into it on xenserver, which uses i686
centos 5.2 for the dom0, inexcusably.
In case it's ever useful in identifying this class of broken du
- Original Message -
>
> On the off-chance that you've hit this particular one (there's no
> clear indication) - taking a dump of a 64-bit guest from a 32-bit
> host will not work. libxc bug that gave me no end of grief.
Interesting...
I noticed that he used a 32-bit HVM guest an exa
- Original Message -
>
>
> my crash can analyse xen hvm guest linux memory dump core :
>
>
> SLES11:/mnt/sles10.2_crash # crash32 -s vmlinux-debug sles10.img
> WARNING: kernel version inconsistency between vmlinux and dumpfile
>
> crash32> bt
> PID: 0 TASK: c02d8280 CPU: 0 COMMAND: "
On the off-chance that you've hit this particular one (there's no clear
indication) - taking a dump of a 64-bit guest from a 32-bit host will not
work. libxc bug that gave me no end of grief.
--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utilit
- Original Message -
>
>
> SLES11:/opt/kdump # nm -Bn vmlinux | grep -e 806f7360 -e
> 80674690
> 80674690 B phys_to_machine_mapping
> 806f7360 B max_pfn
>
> 806f7360 should be "end_pfn" or "max_pfn", you are right!
OK, so this is one of the "old
my crash can analyse xen hvm guest linux memory dump core :
SLES11:/mnt/sles10.2_crash # crash32 -s vmlinux-debug sles10.img
WARNING: kernel version inconsistency between vmlinux and dumpfile
crash32> bt
PID: 0 TASK: c02d8280 CPU: 0 COMMAND: "swapper"
#0 [c0329f9c] schedule at c0288d
12 matches
Mail list logo
