All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minjun Hong <nickeysgo@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: crashdump on PVM Dom0
Date: Mon, 28 Aug 2017 19:45:23 +0900	[thread overview]
Message-ID: <CAFX_q-HeR3MUnwJCX094kNKhQXP7NbJh80LUM4wdizoVXj9_Mw@mail.gmail.com> (raw)
In-Reply-To: <59A3FAF202000078001746B4@prv-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1350 bytes --]

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?

Sincerely,

On Mon, Aug 28, 2017 at 6:13 PM, Jan Beulich <JBeulich@suse.com> wrote:

> >>> On 28.08.17 at 11:04, <nickeysgo@gmail.com> wrote:
> > Thank you for your reply.
> > I checked what you mentioned(Xen command line).
> > But I could not find where the Xen command line configuration.
> > As I think, it would be in /etc/default/grub file because Dom0 is used
> for
> > booting like native system.
> > Is it wrong? I didn't get your point?
>
> First of all - please avoid private mails. Keep the list Cc-ed.
>
> And then - I can't tell you how to configure your variant of grub.
> All I can tell you is that the option you're after needs to be
> passed to Xen.
>
> Jan
>
>

[-- Attachment #1.2: Type: text/html, Size: 2068 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  parent reply	other threads:[~2017-08-28 10:45 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 [this message]
2017-08-28 11:13         ` Jan Beulich
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=CAFX_q-HeR3MUnwJCX094kNKhQXP7NbJh80LUM4wdizoVXj9_Mw@mail.gmail.com \
    --to=nickeysgo@gmail.com \
    --cc=JBeulich@suse.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.