Comment 36 for bug 1400319

To summarize all previous activity on this bug for easier tracking, I've re-done now a check on this bug and here are the details:

Hyper-V: Server 2012 R2
VM: Ubuntu 15.04
Kernel: 3.19.0-15
Default crashkernel value: 384M-:128M
Also verified with crashkernel=384M@384M

Status: kdump-tools is marked as active but displays "Could not find a free area of memory of 0x9f000 bytes..."
/sys/kernel/kexec_crash_loaded is 0
/sys/kernel/kexec_crash_size shows the correct assigned crashkernel value from grub.
Trigerring a kernel panic doesn't do anything given these details.

On 15.04 the latest kexec-tools package version is 2.0.7-5ubuntu2
What I've done was to take the version present in Wily - kexec-tools_2.0.9-1ubuntu1_i386 and installed it on 15.04.

kdump-tools is loading now without the error above, and also kexec_crash_loaded is at 1 now.
Trigerring the panic now, the VM will not reboot nor write the vmcore dump file.

I'm checking now to see that for the problem where the VM doesn't reboot on panic if that is not due to some missing vmbus kdump patches that have been implemented before.
But at least for the error of "Could not find a free area of memory of 0x9f000 bytes...", that seems to be due to the kexec-tools.
Joe can you please have a look at that or assign it to the right contact that is handling that part for some analysis?