From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Daniil Cherednik <dcherednik@roshianokatachi.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Debuging dom0, oops while kexec
Date: Fri, 21 Jun 2013 13:32:50 +0100 [thread overview]
Message-ID: <51C447F2.5050805@citrix.com> (raw)
In-Reply-To: <48da1ce0247529c7a5b61356de63eab9@roshianokatachi.com>
On 21/06/13 13:01, Daniil Cherednik wrote:
> Hello!
>
> We use ubuntu 12.04 on dom0 xen-4.1, linux-3.5
> We have some issue with our hardware driver, and I need to get dom0
> coredump. But when I was trying to configure kdump it was unsuccessful
> and I used kexec -l ... to diagnostic the issue I got oops like
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1807
> Also I noticed recently it was discussing about implementation kexec
> mechanism in hypervisor without involving dom0 kernel...
> So I will be grateful if someone can take me any advises about using
> kexec with xen and about bug1807
>
> Best regards,
> Daniil Cherednik
First of all, you want -p for a crash kernel, not -l (which is a load
kernel).
That link shows a linux-3.5 bug. At a guess machine_kexec_prepare is
not suitably sanitising some pointers before trying to use them.
There are patch series for Xen (and libxc) and kexec tools. The Xen
patch series is being deferred until Xen 4.4 development starts. The
kexec tools series also needs to wait until the libxc patches are available.
The slight problem with this approach is that you need to patch the
kernel to unconditionally issue a kexec hypercall as it no longer knows
whether a crash image has been loaded or not.
~Andrew
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-06-21 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 12:01 Debuging dom0, oops while kexec Daniil Cherednik
2013-06-21 12:32 ` Andrew Cooper [this message]
2013-06-21 13:30 ` David Vrabel
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=51C447F2.5050805@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dcherednik@roshianokatachi.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.