From: "Jan Beulich" <JBeulich@suse.com>
To: Minjun Hong <nickeysgo@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: crashdump on PVM Dom0
Date: Mon, 28 Aug 2017 05:13:49 -0600 [thread overview]
Message-ID: <59A4170D0200007800174800@prv-mh.provo.novell.com> (raw)
In-Reply-To: <CAFX_q-HeR3MUnwJCX094kNKhQXP7NbJh80LUM4wdizoVXj9_Mw@mail.gmail.com>
>>> On 28.08.17 at 12:45, <nickeysgo@gmail.com> wrote:
> Oh!! I'm so sorry Jan Beulich.
> It is my first time to use this mailing list.
> Please understand my fault, this time only.
>
> Anyway, as you mentioned, I added below line in '/etc/default/grub' file
> and reboot:
>> GRUB_CMDLINE_XEN="crashkernel=384M-:256M@64M"
> Then,
> 1. I cannot see anything when I type "grep -i crash /proc/iomem"
> 2. I can see kernel log of Xen hypervisor when I type "sudo xl dmesg | grep
> -i crash":
> (XEN) Command line: placeholder crashkernel=384M-:256M@64M
>
> I suppose a 'crashkernel' cmdline option of either Xen hypervisor or Dom0
> kernel can be enabled.
> I know it is quite difficult to advise some problems online but, could you
> give me a piece of hint?
I'm not sure what else hint you're after. You can check the log
so see whether the option was accepted. I'm not sure /proc/iomem
is supposed to have any indication of the crash area.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-28 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 8:01 crashdump on PVM Dom0 Minjun Hong
2017-08-28 8:13 ` Jan Beulich
[not found] ` <CAFX_q-HHBCb6KOknVXhu5CirfEckkOS0SW2ZLjoaEcpswwy5Og@mail.gmail.com>
[not found] ` <59A3FAF202000078001746B4@prv-mh.provo.novell.com>
2017-08-28 10:45 ` Minjun Hong
2017-08-28 11:13 ` Jan Beulich [this message]
2017-08-29 9:19 ` Wei Liu
2017-08-29 10:05 ` Roger Pau Monné
2017-08-29 10:24 ` Minjun Hong
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=59A4170D0200007800174800@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=nickeysgo@gmail.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.