------- Comment From <email address hidden> 2017-03-21 13:08 EDT-------
(In reply to comment #5)
> /proc/vmcore is generated by kdump support in the kernel. This might not be
> a bug, but a case of missing support for regenerating /proc/vmcore entries
> after DLPAR memory removal.
True. kdump needs to be reloaded after a DLPAR operation to
regenerate /proc/vmcore entries. So, kdump-tools.service needs
to be restarted after a DLPAR operation.
Simialr bug raised against 16.04.2 - https://bugs.launchpad.net/bugs/1655280
------- Comment From <email address hidden> 2017-03-21 13:08 EDT-------
(In reply to comment #5)
> /proc/vmcore is generated by kdump support in the kernel. This might not be
> a bug, but a case of missing support for regenerating /proc/vmcore entries
> after DLPAR memory removal.
True. kdump needs to be reloaded after a DLPAR operation to /bugs.launchpad .net/bugs/ 1655280
regenerate /proc/vmcore entries. So, kdump-tools.service needs
to be restarted after a DLPAR operation.
Simialr bug raised against 16.04.2 - https:/
Thanks
Hari