On Fri, Jan 04, 2013 at 02:41:17PM +0000, Jan Beulich wrote:
quoted
quoted
quoted
On 04.01.13 at 15:22, Daniel Kiper [off-list ref] wrote:
On Wed, Jan 02, 2013 at 11:26:43AM +0000, Andrew Cooper wrote:
quoted
/sbin/kexec can load the "Xen" crash kernel itself by issuing
hypercalls using /dev/xen/privcmd. This would remove the need for
the dom0 kernel to distinguish between loading a crash kernel for
itself and loading a kernel for Xen.
Or is this just a silly idea complicating the matter?
This is impossible with current Xen kexec/kdump interface.
Why?
Because current KEXEC_CMD_kexec_load does not load kernel
image and other things into Xen memory. It means that it
should live somewhere in dom0 Linux kernel memory.
Daniel