From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: Sven Anders <anders@anduras.de>, kexec@lists.infradead.org
Subject: Re: newbie question: kexec linux-based bootstrap
Date: Mon, 12 Jan 2009 15:15:59 -0800 [thread overview]
Message-ID: <496BCF2F.1060700@oracle.com> (raw)
In-Reply-To: <F795765B112E7344AF36AA911279641508F6B42E@xmb-sjc-212.amer.cisco.com>
Bizhan Gholikhamseh (bgholikh) wrote:
>> You enabled kexec in the new kernel that you are trying to load or in
>> the first/running kernel? It appears that kexec is not loaded in the
>> first/running kernel, but it must be enabled for kexec-tools to work
>> correctly.
>
> Yes, that was the problem, now I am getting a new error, I do not care
> for crash dump, but when I execute kexec -e it ask me to reserve some
> space for it and use kdump kernel, which is not the case I am
> interested:
>
> # ./kexec -e -append="root/dev/sdb2"
> Memory for crashkernel is not reserved
> Please reserve memory by passing "crashkernel=X@Y" parameter to the
> kernel
> Then try loading kdump kernel
>
>
> ???
You still need to reserve space for the new kernel to be loaded into.
It has to be loaded into memory before it is needed.
Those messages that say "crashkernel" can be misleading, but that's
what the kernel parameter is named.
--
~Randy
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-01-12 23:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 11:29 newbie question: kexec linux-based bootstrap Bizhan Gholikhamseh (bgholikh)
2009-01-12 13:09 ` Sven Anders
2009-01-12 22:00 ` Bizhan Gholikhamseh (bgholikh)
2009-01-12 22:04 ` Randy Dunlap
2009-01-12 22:44 ` Bizhan Gholikhamseh (bgholikh)
2009-01-12 22:54 ` Randy Dunlap
2009-01-12 23:07 ` Bizhan Gholikhamseh (bgholikh)
2009-01-12 23:15 ` Randy Dunlap [this message]
2009-01-13 4:32 ` M. Mohan Kumar
2009-01-13 14:49 ` David N. Lombard
2009-01-13 15:42 ` Bizhan Gholikhamseh (bgholikh)
2009-01-13 16:43 ` David N. Lombard
2009-01-13 18:41 ` Geoff Levand
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=496BCF2F.1060700@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=anders@anduras.de \
--cc=bgholikh@cisco.com \
--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