Kdump is enabled in the config file at /etc/default/kdump-tools
Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m | 384M-:256M
VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this in combination with the values for crashkernel.
Trying to start the kdump service:
root@ubuntu1410i386:~# /etc/init.d/kdump-tools start
Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes...
locate_hole failed
* failed to load kdump kernel
---
If the conversion from hex to dec is right, the mentioned memory mapping of 0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then related to the RAM allocation nor the crashkernel value used.
While testing the final build of 14.10 32bit we found that kernel panic cannot be activated for an installation on a Hyper-V VM.
Repro rate: 100%
Repro details:
Hyper-V: Server 2012 R2
VM: Ubuntu 14.10 32bit
Kdump is enabled in the config file at /etc/default/ kdump-tools
Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m | 384M-:256M
VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this in combination with the values for crashkernel.
Trying to start the kdump service: i386:~# /etc/init. d/kdump- tools start
root@ubuntu1410
Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes...
locate_hole failed
* failed to load kdump kernel
---
root@ubuntu1410 i386:~# cat /sys/kernel/ kexec_crash_ loaded
0
If the conversion from hex to dec is right, the mentioned memory mapping of 0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then related to the RAM allocation nor the crashkernel value used.