[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 2/2] Allow kdump with crash_kexec_post_notifiers


  • To: "Jan Beulich" <JBeulich@xxxxxxxx>
  • From: Petr Tesarik <ptesarik@xxxxxxxx>
  • Date: Mon, 1 Aug 2016 15:02:50 +0200
  • Cc: XEN
  • Delivery-date: Mon, 01 Aug 2016 13:06:05 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Mon, 1 Aug 2016 13:55:01 +0200
"Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> >>> On 13.07.16 at 14:53, <david.vrabel@xxxxxxxxxx> wrote:
> > On 13/07/16 13:20, Petr Tesarik wrote:
> >> If a crash kernel is loaded, do not crash the running domain. This is
> >> needed if the kernel is loaded with crash_kexec_post_notifiers, because
> >> panic notifiers are run before __crash_kexec() in that case, and this
> >> Xen hook prevents its being called later.
> > 
> > Prioritising the in-kernel kexec image over the hypervisor one seems
> > sensible behaviour to me.
> 
> For HVM guests certainly; does loading of an in-kernel crash kernel
> properly fail for PV guests (and namely PV Dom0), or does such a
> setup work nowadays?

This is a good question, but I don't think it is relevant to this
patch. It does not change anything unless the kernel is booted with
crash_kexec_post_notifiers.

I fully understand that Dom0 kernels want to load the panic kernel in
the hypervisor and crash the complete machine, rather than just Dom0,
but if you want that behaviour, simply pass the "crashkernel="
parameter only to the Xen hypervisor and not to the Dom0 kernel.

Did I miss something?

Petr T

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.