public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@overnetdata.com>
To: David Vrabel <david.vrabel@citrix.com>, WANG Chao <chaowang@redhat.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
	Simon Horman <horms@verge.net.au>,
	kexec@lists.infradead.org
Subject: Re: Can't load bzImage crashkernel on xen system with 32 bit kernel
Date: Fri, 11 Jul 2014 12:27:40 +0100	[thread overview]
Message-ID: <53BFCA2C.6010403@overnetdata.com> (raw)
In-Reply-To: <53BFB093.10307@citrix.com>

On 11/07/2014 10:38, David Vrabel wrote:
> On 11/07/14 08:58, WANG Chao wrote:
>> On 07/10/14 at 11:11am, Anthony Wright wrote:
>>> Hi Chao,
>>>
>>> Thanks for looking at this.
>>>
>>> On 10/07/2014 08:47, WANG Chao wrote:
>>>> Hi, Anthony
>>>>
>>>> On 07/08/14 at 11:34am, Anthony Wright wrote:
>>>>> After successfully modifying kexec-tools to get it to load a crashkernel
>>>>> on a standard 32 bit linux 3.10.17 kernel, I tried to get it to load the
>>>>> same crashkernel on the same 32 bit linux kernel running under xen
>>>>> 4.4.0, but get the error "Cannot load <kernel-path>".
> Are you trying to do an in-guest kexec or are you trying to kexec from Xen?
>
> If it's the latter, it should just work with 32 and 64-bit images, Xen
> 4.4 and kexec-tools 2.0.5 or later.
>
> In-guest kexec doesn't work at all.
>
> David
I'm trying to do the kexec from within a 32 bit linux 3.10.17 Dom0
running under a 64 bit xen 4.4.0. When you say 'guest', does that mean
DomU's or does that include Dom0 as well? If it includes Dom0 could you
point me at some documentation to explain how/if it's possible to set up
kexec/kdump for Dom0.

I have a Dom0 kernel that's crashing infrequently. I can't reproduce it
easily and all the standard diagnostic techniques haven't been very
helpful. I'd hoped to generate a crashdump using kexec/kdump to help
diagnose the problem.

Anthony.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-07-11 11:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 10:34 Can't load bzImage crashkernel on xen system with 32 bit kernel Anthony Wright
2014-07-10  7:47 ` WANG Chao
2014-07-10 10:11   ` Anthony Wright
2014-07-11  7:58     ` WANG Chao
2014-07-11  9:38       ` David Vrabel
2014-07-11 11:27         ` Anthony Wright [this message]
2014-07-11 12:17           ` David Vrabel
2014-07-14 11:01             ` Anthony Wright
2014-07-30  9:52               ` David Vrabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53BFCA2C.6010403@overnetdata.com \
    --to=anthony@overnetdata.com \
    --cc=chaowang@redhat.com \
    --cc=daniel.kiper@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox