All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minjun Hong <nickeysgo@gmail.com>
To: xen-devel@lists.xen.org
Subject: crashdump on PVM Dom0
Date: Mon, 28 Aug 2017 17:01:48 +0900	[thread overview]
Message-ID: <CAFX_q-Fk2eh6aNa+EvB4qeyarmJFq9aEbPQP7xfV2tH9bxzumQ@mail.gmail.com> (raw)


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

Hello~
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
> "
> # update-grub2
> # reboot
>

5. Problem:
- current state is "not ready to kdump" when I type "kdump-config show":

> DUMP_MODE:        kdump
> USE_KDUMP:        1
> KDUMP_SYSCTL:     kernel.panic_on_oops=1
> KDUMP_COREDIR:    /var/crash
> crashkernel addr: 0x30000000
> current state:    Not ready to kdump
>

I have done my best to resolve this problem, but I don't have any other way
that I could try anymore.
If you have a hint which helps me use crashdump on PVM Dom0 or any other
way to debug customized Xen that it causes automatic reboot of Dom0 due to
wrong code modification(without any log),
please let me know.
Even if it is very minor thing, I'll really appreciate it.

Thanks to read this.
Sincerely,

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

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

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

             reply	other threads:[~2017-08-28  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28  8:01 Minjun Hong [this message]
2017-08-28  8:13 ` crashdump on PVM Dom0 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
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-Fk2eh6aNa+EvB4qeyarmJFq9aEbPQP7xfV2tH9bxzumQ@mail.gmail.com \
    --to=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.