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 02:13:17 -0600 [thread overview]
Message-ID: <59A3ECBD0200007800174564@prv-mh.provo.novell.com> (raw)
In-Reply-To: <CAFX_q-Fk2eh6aNa+EvB4qeyarmJFq9aEbPQP7xfV2tH9bxzumQ@mail.gmail.com>
>>> On 28.08.17 at 10:01, <nickeysgo@gmail.com> wrote:
> I'm new to develop Xen and my first work is about its scheduler.
> After I modified Xen 4.5 source code, my custom Xen has had a problem,
> which it causes automatic reboot of Dom0 when I execute a micro benchmark
> program.
> To debug it, I have tried to use crashdump on Dom0 with the Xen but, I
> failed to enable it.
> My configurations are following:
>
> 1. Base Xen version: 4.5 release
> 2. OS: Ubuntu 14.04 LTS
> 3. VM type: PVM
>
> 4. Crashdump install:
> - install linux-crashdump
> - install kexec from source code with '--with-xen' option
> - modified '/etc/default/kdump-tools':
>
>> USE_KDUMP=1
>>
> - kernel boot param setting(/etc/defualt/grub):
>
>>
>>
> GRUB_CMDLINE_LINUX="crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G
> :2048M,128G-:4096M@32M
It is Xen to control the reserved memory, so "crashkernel=" needs
to be put on the Xen command line (suitably modified to that Xen
actually understands it - see the command line option documentation).
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 8: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 [this message]
[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
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=59A3ECBD0200007800174564@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.