I've just tested triggering a crash dump and it didn't work. A Google search pointed me to this bug. When I see /boot on a separate partition, I just realized it is the damn case! Others like dbgsym kernel from ddeb, kdump-tools, linux-crashdump all installed and properly configured.
The VMs use LVM so they all have a separate /boot partition, that's why kdump was not able to dump the /proc/vmcore.
After using the workaround (umount /boot and use the /boot on /), it worked!
However, there is no 0_dump file under /usr/share/initramfs-tools/scripts/init-bottom/ WTF? So what is causing the problem in Ubuntu 14.04 with a separate /boot partition?
Is this really fixed on Ububuntu 14.04 LTS?
I've just tested triggering a crash dump and it didn't work. A Google search pointed me to this bug. When I see /boot on a separate partition, I just realized it is the damn case! Others like dbgsym kernel from ddeb, kdump-tools, linux-crashdump all installed and properly configured.
The VMs use LVM so they all have a separate /boot partition, that's why kdump was not able to dump the /proc/vmcore.
After using the workaround (umount /boot and use the /boot on /), it worked!
However, there is no 0_dump file under /usr/share/ initramfs- tools/scripts/ init-bottom/ WTF? So what is causing the problem in Ubuntu 14.04 with a separate /boot partition?
A separate bug needed?