Skip to contentSkip to conversation

Can't load bzImage crashkernel on xen system with 32 bit kernel

DISCUSSION Anthony Wright 3 participants 9 messages Jul 8, 2014 – Jul 30, 2014

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

I've patched the code to include some diagnostics, and the problem is caused by add_memmap() reporting that it's been called with overlapping memory.

It's called twice, the first time it's called with:

	address: 0x00000000
	size:    0x0009f800
	type:    0

This comes from info->backup_src_*

The second time it is passed

	address: 0x00000000
	size:    0x00000000
	type:    0

This is derived from the crash_reserved_mem[] array, which has one element with the values:

	start: 0x0000000000000000 (16 0's)
	end:   0xffffffffffffffff (16 f's)

The problem isn't caused by the zero size because the maths in add_memmap, uses size to calculate end which overflows back again, and (partially) cancels out the error. The problem is caused by the two memory blocks being based at 0x0, causing the blocks to overlap.

I'm not sure what the correct functionality should be.

Thanks,

Anthony.

Signature · 8 lines
Founder, Overnet Data Ltd
+44-1604-807545
www.overnetdata.com

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
#1 lore raw

Hi, Anthony

Quoted 17 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

I've patched the code to include some diagnostics, and the problem is caused by add_memmap() reporting that it's been called with overlapping memory.

It's called twice, the first time it's called with:

	address: 0x00000000
	size:    0x0009f800
	type:    0

This comes from info->backup_src_*

The second time it is passed

Quoted 8 lines
	address: 0x00000000
	size:    0x00000000
	type:    0

This is derived from the crash_reserved_mem[] array, which has one element with the values:

	start: 0x0000000000000000 (16 0's)
	end:   0xffffffffffffffff (16 f's)

Why it looks like that? crashkernel memory region shouldn't be that extreme.

Maybe there's something wrong when it retrieves crashkernel reserved region. How you does your /proc/iomem look like?

Turn on debug option (-d) would be helpful too.

Quoted 5 lines

The problem isn't caused by the zero size because the maths in add_memmap, uses size to calculate end which overflows back again, and (partially) cancels out the error. The problem is caused by the two memory blocks being based at 0x0, causing the blocks to overlap.

The overflow issue should be easy to fix once we figure out why the crash_reserved_mem[] has a element like that.

Thanks
WANG Chao

Quoted 17 lines

I'm not sure what the correct functionality should be.

Thanks,

Anthony.

Signature · 8 lines
Founder, Overnet Data Ltd
+44-1604-807545
www.overnetdata.com

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#2 lore raw

Hi Chao,

Thanks for looking at this.

Quoted 24 lines · WANG Chao

Hi, Anthony

Quoted 21 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

I've patched the code to include some diagnostics, and the problem is caused by add_memmap() reporting that it's been called with overlapping memory.

It's called twice, the first time it's called with:

	address: 0x00000000
	size:    0x0009f800
	type:    0

This comes from info->backup_src_*

The second time it is passed

	address: 0x00000000
	size:    0x00000000
	type:    0
Quoted 6 lines
Quoted 4 lines

This is derived from the crash_reserved_mem[] array, which has one element with the values:

	start: 0x0000000000000000 (16 0's)
	end:   0xffffffffffffffff (16 f's)

Why it looks like that? crashkernel memory region shouldn't be that extreme.

Is it something to do with xen 4.4.0? The xen hypervisor is 64 bit, but the Dom0 linux kernel is 32 bit. I realise this is a bit of a strange combination, but we run this way for historical reasons.

Quoted 4 lines

Maybe there's something wrong when it retrieves crashkernel reserved region. How you does your /proc/iomem look like?

Turn on debug option (-d) would be helpful too.

I've attached a copy of /proc/iomem and the output of kexec with the -d flag.

Quoted 9 lines
Quoted 4 lines

The problem isn't caused by the zero size because the maths in add_memmap, uses size to calculate end which overflows back again, and (partially) cancels out the error. The problem is caused by the two memory blocks being based at 0x0, causing the blocks to overlap.

The overflow issue should be easy to fix once we figure out why the crash_reserved_mem[] has a element like that.

Thanks
WANG Chao

thanks,

Anthony.

00000000-00000fff : reserved
00001000-0009efff : System RAM
0009f000-0009f7ff : RAM buffer
0009f800-000fffff : reserved
000a0000-000bffff : PCI Bus 0000:00
000c0000-000cebff : Video ROM
000d0000-000dffff : PCI Bus 0000:00
000f0000-000fffff : System ROM
00100000-cff9ffff : System RAM
01000000-015897cd : Kernel code
015897ce-0182debf : Kernel data
018e6000-019bbfff : Kernel bss
18000000-1fffffff : Crash kernel
cffa0000-cffaffff : ACPI Tables
cffb0000-cffdffff : ACPI Non-volatile Storage
cffe0000-cfffffff : reserved
d0000000-dfffffff : PCI Bus 0000:00
d0000000-dfffffff : PCI Bus 0000:01

    d0000000-dfffffff : 0000:01:05.0

e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff]
e0000000-efffffff : pnp 00:0c
f0000000-febfffff : PCI Bus 0000:00
fdf00000-fdffffff : PCI Bus 0000:03

    fdff8000-fdffbfff : 0000:03:00.0
      fdff8000-fdffbfff : r8169
    fdfff000-fdffffff : 0000:03:00.0
      fdfff000-fdffffff : r8169
  fe7f4000-fe7f7fff : 0000:00:14.2
  fe7fa000-fe7fafff : 0000:00:14.5
    fe7fa000-fe7fafff : ohci_hcd
  fe7fb000-fe7fbfff : 0000:00:13.1
    fe7fb000-fe7fbfff : ohci_hcd
  fe7fc000-fe7fcfff : 0000:00:13.0
    fe7fc000-fe7fcfff : ohci_hcd
  fe7fd000-fe7fdfff : 0000:00:12.1
    fe7fd000-fe7fdfff : ohci_hcd
  fe7fe000-fe7fefff : 0000:00:12.0
    fe7fe000-fe7fefff : ohci_hcd
  fe7ff400-fe7ff4ff : 0000:00:13.2
    fe7ff400-fe7ff4ff : ehci_hcd
  fe7ff800-fe7ff8ff : 0000:00:12.2
    fe7ff800-fe7ff8ff : ehci_hcd
  fe7ffc00-fe7fffff : 0000:00:11.0
    fe7ffc00-fe7fffff : ahci
  fe800000-fe9fffff : PCI Bus 0000:01
    fe800000-fe8fffff : 0000:01:05.0
    fe9f0000-fe9fffff : 0000:01:05.0
  fea00000-feafffff : PCI Bus 0000:02
    feaff800-feafffff : 0000:02:00.0
      feaff800-feafffff : firewire_ohci
  feb00000-febfffff : PCI Bus 0000:03
    febe0000-febfffff : 0000:03:00.0

fec00000-fec003ff : IOAPIC 0
fec10000-fec1001f : pnp 00:08
fee00000-feefffff : reserved
fee00000-fee00fff : Local APIC

    fee00000-fee00fff : pnp 00:07

ffb80000-ffbfffff : pnp 00:08
fff00000-ffffffff : reserved
100000000-21fffffff : System RAM
fd00000000-ffffffffff : reserved

kernel: 0xb6dbb008 kernel_size: 0x3b09f0
MEMORY RANGES
0000000000000100-000000000009f7ff (0) 000000000009f800-000000000009ffff (1) 00000000000e7000-00000000000fffff (1) 0000000000100000-00000000cff9ffff (0) 00000000cffa0000-00000000cffaffff (2) 00000000cffb0000-00000000cffdffff (3) 00000000cffe0000-00000000cfffffff (1) 00000000fee00000-00000000feefffff (1) 00000000fff00000-00000000ffffffff (1) 0000000100000000-000000021fffffff (0) 000000fd00000000-000000ffffffffff (1)
bzImage is relocatable
get_backup_area: 0000000000000000-000000000009f7ff : System RAM CRASH MEMORY RANGES
0000000000000000-000000000009f7ff (0) 000000000009f800-ffffffffffffffff (1) 00000000000e7000-ffffffffffffffff (1) 0000000000100000-ffffffffffffffff (0) 0000000038000000-ffffffffffffffff (0) 00000000cffa0000-ffffffffffffffff (2) 00000000cffb0000-ffffffffffffffff (3) 00000000cffe0000-ffffffffffffffff (1) 00000000fee00000-ffffffffffffffff (1) 00000000fff00000-ffffffffffffffff (1) 0000000100000000-ffffffffffffffff (0) 000000fd00000000-ffffffffffffffff (1) 0000000000000000-000000ffffffffff (0)
Memmap after adding segment 0000000000000000-000000000009f7ff (0)
Cannot load /boot/master/XenMaster-6.9.0/kernel

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#3 lore raw
Quoted 140 lines · Anthony Wright

Hi Chao,

Thanks for looking at this.

Quoted 24 lines · WANG Chao

Hi, Anthony

Quoted 21 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

I've patched the code to include some diagnostics, and the problem is caused by add_memmap() reporting that it's been called with overlapping memory.

It's called twice, the first time it's called with:

	address: 0x00000000
	size:    0x0009f800
	type:    0

This comes from info->backup_src_*

The second time it is passed

	address: 0x00000000
	size:    0x00000000
	type:    0
Quoted 6 lines
Quoted 4 lines

This is derived from the crash_reserved_mem[] array, which has one element with the values:

	start: 0x0000000000000000 (16 0's)
	end:   0xffffffffffffffff (16 f's)

Why it looks like that? crashkernel memory region shouldn't be that extreme.

Is it something to do with xen 4.4.0? The xen hypervisor is 64 bit, but the Dom0 linux kernel is 32 bit. I realise this is a bit of a strange combination, but we run this way for historical reasons.

Quoted 4 lines

Maybe there's something wrong when it retrieves crashkernel reserved region. How you does your /proc/iomem look like?

Turn on debug option (-d) would be helpful too.

I've attached a copy of /proc/iomem and the output of kexec with the -d flag.

Quoted 9 lines
Quoted 4 lines

The problem isn't caused by the zero size because the maths in add_memmap, uses size to calculate end which overflows back again, and (partially) cancels out the error. The problem is caused by the two memory blocks being based at 0x0, causing the blocks to overlap.

The overflow issue should be easy to fix once we figure out why the crash_reserved_mem[] has a element like that.

Thanks
WANG Chao

thanks,

Anthony.

00000000-00000fff : reserved
00001000-0009efff : System RAM
0009f000-0009f7ff : RAM buffer
0009f800-000fffff : reserved
000a0000-000bffff : PCI Bus 0000:00
000c0000-000cebff : Video ROM
000d0000-000dffff : PCI Bus 0000:00
000f0000-000fffff : System ROM
00100000-cff9ffff : System RAM
01000000-015897cd : Kernel code
015897ce-0182debf : Kernel data
018e6000-019bbfff : Kernel bss
18000000-1fffffff : Crash kernel
cffa0000-cffaffff : ACPI Tables
cffb0000-cffdffff : ACPI Non-volatile Storage
cffe0000-cfffffff : reserved
d0000000-dfffffff : PCI Bus 0000:00
d0000000-dfffffff : PCI Bus 0000:01

    d0000000-dfffffff : 0000:01:05.0

e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff]
e0000000-efffffff : pnp 00:0c
f0000000-febfffff : PCI Bus 0000:00
fdf00000-fdffffff : PCI Bus 0000:03

    fdff8000-fdffbfff : 0000:03:00.0
      fdff8000-fdffbfff : r8169
    fdfff000-fdffffff : 0000:03:00.0
      fdfff000-fdffffff : r8169
  fe7f4000-fe7f7fff : 0000:00:14.2
  fe7fa000-fe7fafff : 0000:00:14.5
    fe7fa000-fe7fafff : ohci_hcd
  fe7fb000-fe7fbfff : 0000:00:13.1
    fe7fb000-fe7fbfff : ohci_hcd
  fe7fc000-fe7fcfff : 0000:00:13.0
    fe7fc000-fe7fcfff : ohci_hcd
  fe7fd000-fe7fdfff : 0000:00:12.1
    fe7fd000-fe7fdfff : ohci_hcd
  fe7fe000-fe7fefff : 0000:00:12.0
    fe7fe000-fe7fefff : ohci_hcd
  fe7ff400-fe7ff4ff : 0000:00:13.2
    fe7ff400-fe7ff4ff : ehci_hcd
  fe7ff800-fe7ff8ff : 0000:00:12.2
    fe7ff800-fe7ff8ff : ehci_hcd
  fe7ffc00-fe7fffff : 0000:00:11.0
    fe7ffc00-fe7fffff : ahci
  fe800000-fe9fffff : PCI Bus 0000:01
    fe800000-fe8fffff : 0000:01:05.0
    fe9f0000-fe9fffff : 0000:01:05.0
  fea00000-feafffff : PCI Bus 0000:02
    feaff800-feafffff : 0000:02:00.0
      feaff800-feafffff : firewire_ohci
  feb00000-febfffff : PCI Bus 0000:03
    febe0000-febfffff : 0000:03:00.0

fec00000-fec003ff : IOAPIC 0
fec10000-fec1001f : pnp 00:08
fee00000-feefffff : reserved
fee00000-fee00fff : Local APIC

    fee00000-fee00fff : pnp 00:07

ffb80000-ffbfffff : pnp 00:08
fff00000-ffffffff : reserved
100000000-21fffffff : System RAM
fd00000000-ffffffffff : reserved

kernel: 0xb6dbb008 kernel_size: 0x3b09f0
MEMORY RANGES
0000000000000100-000000000009f7ff (0) 000000000009f800-000000000009ffff (1) 00000000000e7000-00000000000fffff (1) 0000000000100000-00000000cff9ffff (0) 00000000cffa0000-00000000cffaffff (2) 00000000cffb0000-00000000cffdffff (3) 00000000cffe0000-00000000cfffffff (1) 00000000fee00000-00000000feefffff (1) 00000000fff00000-00000000ffffffff (1) 0000000100000000-000000021fffffff (0) 000000fd00000000-000000ffffffffff (1)
bzImage is relocatable
get_backup_area: 0000000000000000-000000000009f7ff : System RAM CRASH MEMORY RANGES
0000000000000000-000000000009f7ff (0) 000000000009f800-ffffffffffffffff (1) 00000000000e7000-ffffffffffffffff (1) 0000000000100000-ffffffffffffffff (0) 0000000038000000-ffffffffffffffff (0)

Quoted 8 lines

00000000cffa0000-ffffffffffffffff (2)
00000000cffb0000-ffffffffffffffff (3)
00000000cffe0000-ffffffffffffffff (1)
00000000fee00000-ffffffffffffffff (1)
00000000fff00000-ffffffffffffffff (1)
0000000100000000-ffffffffffffffff (0)
000000fd00000000-ffffffffffffffff (1)
0000000000000000-000000ffffffffff (0)

Above doesn't look right to me. kexec is using Xen hypercall to get these memory region. I'm not able to get kexec to work on box because at the verify beginning get_xc_kexec_get_range returns -1. And I'm not familiar with Xen.

CC some authors of kexec/Xen. They might help you on this.

Thanks
WANG Chao

Quoted 3 lines

Memmap after adding segment
0000000000000000-000000000009f7ff (0)
Cannot load /boot/master/XenMaster-6.9.0/kernel

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#4 lore raw
Quoted 5 lines · WANG Chao
Quoted 4 lines · Anthony Wright

Hi Chao,

Thanks for looking at this.

Quoted 8 lines
Quoted 8 lines · WANG Chao
Quoted 7 lines

Hi, Anthony

Quoted 4 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

Are you trying to do an in-guest kexec or are you trying to kexec from Xen?

If it's the latter, it should just work with 32 and 64-bit images, Xen 4.4 and kexec-tools 2.0.5 or later.

In-guest kexec doesn't work at all.

David

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#5 lore raw
Quoted 14 lines · David Vrabel
Quoted 5 lines · WANG Chao
Quoted 4 lines · Anthony Wright

Hi Chao,

Thanks for looking at this.

Quoted 8 lines
Quoted 8 lines · WANG Chao
Quoted 7 lines

Hi, Anthony

Quoted 4 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

Quoted 8 lines

Are you trying to do an in-guest kexec or are you trying to kexec from Xen?

If it's the latter, it should just work with 32 and 64-bit images, Xen 4.4 and kexec-tools 2.0.5 or later.

In-guest kexec doesn't work at all.

David

I'm trying to do the kexec from within a 32 bit linux 3.10.17 Dom0 running under a 64 bit xen 4.4.0. When you say 'guest', does that mean DomU's or does that include Dom0 as well? If it includes Dom0 could you point me at some documentation to explain how/if it's possible to set up kexec/kdump for Dom0.

I have a Dom0 kernel that's crashing infrequently. I can't reproduce it easily and all the standard diagnostic techniques haven't been very helpful. I'd hoped to generate a crashdump using kexec/kdump to help diagnose the problem.

Anthony.

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#6 lore raw
Quoted 29 lines · Anthony Wright
Quoted 14 lines · David Vrabel
Quoted 5 lines · WANG Chao
Quoted 4 lines · Anthony Wright

Hi Chao,

Thanks for looking at this.

Quoted 8 lines
Quoted 8 lines · WANG Chao
Quoted 7 lines

Hi, Anthony

Quoted 4 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

Quoted 8 lines

Are you trying to do an in-guest kexec or are you trying to kexec from Xen?

If it's the latter, it should just work with 32 and 64-bit images, Xen 4.4 and kexec-tools 2.0.5 or later.

In-guest kexec doesn't work at all.

David

I'm trying to do the kexec from within a 32 bit linux 3.10.17 Dom0 running under a 64 bit xen 4.4.0. When you say 'guest', does that mean DomU's or does that include Dom0 as well? If it includes Dom0 could you point me at some documentation to explain how/if it's possible to set up kexec/kdump for Dom0.

Quoted 4 lines

I have a Dom0 kernel that's crashing infrequently. I can't reproduce it easily and all the standard diagnostic techniques haven't been very helpful. I'd hoped to generate a crashdump using kexec/kdump to help diagnose the problem.

I would suggest trying a Xen kexec and exec'ing your crashdump kernel (which will then be running on baremetal).

You will need to reserve a region of memory for the crash kernel on the Xen command line (e.g., crashkernel=64M@32M) and use kexec-tools 2.0.5 or later.

We don't actually collect memory dumps from this environment (only basic PCPU/VCPU state, Xen/dom0 backtraces, and console logs) so I'm not sure what the status of tools for this are. Daniel Kiper might know.

David

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#7 lore raw
Quoted 41 lines · David Vrabel
Quoted 29 lines · Anthony Wright
Quoted 14 lines · David Vrabel
Quoted 5 lines · WANG Chao
Quoted 4 lines · Anthony Wright

Hi Chao,

Thanks for looking at this.

Quoted 8 lines
Quoted 8 lines · WANG Chao
Quoted 7 lines

Hi, Anthony

Quoted 4 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

Quoted 8 lines

Are you trying to do an in-guest kexec or are you trying to kexec from Xen?

If it's the latter, it should just work with 32 and 64-bit images, Xen 4.4 and kexec-tools 2.0.5 or later.

In-guest kexec doesn't work at all.

David

I'm trying to do the kexec from within a 32 bit linux 3.10.17 Dom0 running under a 64 bit xen 4.4.0. When you say 'guest', does that mean DomU's or does that include Dom0 as well? If it includes Dom0 could you point me at some documentation to explain how/if it's possible to set up kexec/kdump for Dom0.

Quoted 4 lines

I have a Dom0 kernel that's crashing infrequently. I can't reproduce it easily and all the standard diagnostic techniques haven't been very helpful. I'd hoped to generate a crashdump using kexec/kdump to help diagnose the problem.

I would suggest trying a Xen kexec and exec'ing your crashdump kernel (which will then be running on baremetal).

You will need to reserve a region of memory for the crash kernel on the Xen command line (e.g., crashkernel=64M@32M) and use kexec-tools 2.0.5 or later.

Quoted 5 lines

We don't actually collect memory dumps from this environment (only basic PCPU/VCPU state, Xen/dom0 backtraces, and console logs) so I'm not sure what the status of tools for this are. Daniel Kiper might know.

David

I had the 'crashkernel=128M' parameter on the Dom0 linux kernel cmdline. Removing it from the Dom0 linux kernel command line and placing it on the Xen command line changed things, but unfortunately it still doesn't work.

I get the error message 'failed to get crash region from hypervisor'. On further investigation the call to xc_kexec_get_range() fails returning -1 with an errno of 34 (Numerical result out of range). According to the xen kexec documentation that I could find
(http://xenbits.xen.org/docs/4.4-testing/misc/kexec_and_kdump.txt),
there should be a 'Crash kernel' entry in /proc/iomem, however when I look, no such entry exists. I do wonder if this is an error in the documentation as I would expect a crashkernel= entry on the linux kernel command line to create such an entry in /proc/iomem, but was suprised when the documentation says the entry is created when you put crashkernel= on the xen command line.

On a more fundamental note, are you suggesting that the approach I'm taking simply isn't going to work? I'm trying to solve a problem where a Dom0 kernel running on a machine that I don't have physical access to crashes intermittently with a panic. The on screen part of the panic isn't as helpful as I'd like but it does suggest that the panic is from the disk driver. To give us the best chance of diagnosing the bug I had intended to generate a dump of the kernel after the panic. My plan was to use kexec/kdump to fire up a crash kernel and use that to write the content of the crashed kernel's memory to the filesystem. Once dumped I would reboot and upload the dump.

thanks,

Anthony.

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#8 lore raw
Quoted 46 lines · Anthony Wright
Quoted 45 lines · David Vrabel
Quoted 29 lines · Anthony Wright
Quoted 14 lines · David Vrabel
Quoted 5 lines · WANG Chao
Quoted 4 lines · Anthony Wright

Hi Chao,

Thanks for looking at this.

Quoted 8 lines
Quoted 8 lines · WANG Chao
Quoted 7 lines

Hi, Anthony

Quoted 4 lines · Anthony Wright

After successfully modifying kexec-tools to get it to load a crashkernel on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the same crashkernel on the same 32 bit linux kernel running under xen 4.4.0, but get the error "Cannot load <kernel-path>".

Quoted 8 lines

Are you trying to do an in-guest kexec or are you trying to kexec from Xen?

If it's the latter, it should just work with 32 and 64-bit images, Xen 4.4 and kexec-tools 2.0.5 or later.

In-guest kexec doesn't work at all.

David

I'm trying to do the kexec from within a 32 bit linux 3.10.17 Dom0 running under a 64 bit xen 4.4.0. When you say 'guest', does that mean DomU's or does that include Dom0 as well? If it includes Dom0 could you point me at some documentation to explain how/if it's possible to set up kexec/kdump for Dom0.

Quoted 4 lines

I have a Dom0 kernel that's crashing infrequently. I can't reproduce it easily and all the standard diagnostic techniques haven't been very helpful. I'd hoped to generate a crashdump using kexec/kdump to help diagnose the problem.

I would suggest trying a Xen kexec and exec'ing your crashdump kernel (which will then be running on baremetal).

You will need to reserve a region of memory for the crash kernel on the Xen command line (e.g., crashkernel=64M@32M) and use kexec-tools 2.0.5 or later.

We don't actually collect memory dumps from this environment (only basic PCPU/VCPU state, Xen/dom0 backtraces, and console logs) so I'm not sure what the status of tools for this are. Daniel Kiper might know.

Quoted 5 lines
Quoted 1 line

David

I had the 'crashkernel=128M' parameter on the Dom0 linux kernel cmdline. Removing it from the Dom0 linux kernel command line and placing it on the Xen command line changed things, but unfortunately it still doesn't work.

Try explicitly placing the crash region at a known address as I suggested above.

Quoted 11 lines

I get the error message 'failed to get crash region from hypervisor'. On further investigation the call to xc_kexec_get_range() fails returning -1 with an errno of 34 (Numerical result out of range). According to the xen kexec documentation that I could find
(http://xenbits.xen.org/docs/4.4-testing/misc/kexec_and_kdump.txt),
there should be a 'Crash kernel' entry in /proc/iomem, however when I look, no such entry exists. I do wonder if this is an error in the documentation as I would expect a crashkernel= entry on the linux kernel command line to create such an entry in /proc/iomem, but was suprised when the documentation says the entry is created when you put crashkernel= on the xen command line.

3.x kernels do not add entries into /proc/iomem.

David

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec