mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Kiper <daniel.kiper@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Eric Biederman <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org, Brandon Philips <brandon@ifup.org>,
	xen-devel@lists.xensource.com,
	virtualization@lists.linux-foundation.org
Subject: Re: is kexec on Xen domU possible?
Date: Fri, 19 Jul 2013 15:18:19 +0200	[thread overview]
Message-ID: <20130719131819.GC11233@debian70-amd64.local.net-space.pl> (raw)
In-Reply-To: <20130719020603.GA22932@kroah.com>

On Thu, Jul 18, 2013 at 07:06:03PM -0700, Greg KH wrote:
> Hi all,
>
> I was messing around with kexec and it seems to work just fine on KVM,
> but for Xen domU images, it doesn't work at all.  Daniel, I saw some
> patches from you back in September 2012 for adding this support for
> Dom0, but they don't seem to have gone into the kernel (but other

At first I was going use existing in Xen kexec implementation for Dom0.
However, after some discussion on Xen-devel and LKML we stated that
this implementation is completely broken and should be rewriten. David
Vrabel from Citrix wrote new kexec implementation for Xen which does
not relay on Linux kernel. I hope that it will be included in Xen 4.4 release.

> patches went into kexec-tools at that time.)  You mention that domU

These are mostly fixes which were needed for planned Xen kexec support.
IIRC, they are also needed for systems using ancient Xen Linux Kernel 2.18.
However, most of this implementation will be replaced by new one written
by David Vrabel. It will contain support only for new Xen Dom0 kexec implentation.

> support is "easy" after your patches go in, is that because Dom0 needs
> to support this, or is it something specific to only domU?

In case of domU we should consider following cases:
  - PV guests: there is no support for kexec at this time;
    Once I wrote an implementatation for that type of guests
    for one company but according to our agreement I could not
    publish this code; However, I could use it as a base for
    publicly available kexec implementation; Currently, I do
    not have any plans to work on this due to some more important
    stuff to do; However, question about kexec support for PV
    guests is raised from time to time and maybe this issue
    will be much more important than others once,
  - HVM guests: kexec should work without any issue,
  - PVonHVM guests: IIRC, there were some issues with PV
    drivers but they were fixed some time ago by patches
    posted by Olaf Hering,
  - PVH guests: those type of guests are not available in Xen
    current releases yet; However, Konrad Wilk done some preliminary
    work on kexec support but there are still some issues to resolve.

I do not know what are you trying to do but if you would like
to get some crash dumps there is also another solution to that.
You could use xm/xl dump-core from Dom0 to get dumps of domU memory.

> Also, what's the status of those patches for the kernel, I don't see
> them reposted anywhere, did you drop them?

They were dropped. Please look above for details.

I hope that helps.

Daniel

  reply	other threads:[~2013-07-19 13:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  2:06 Greg KH
2013-07-19 13:18 ` Daniel Kiper [this message]
2013-07-19 13:54   ` Konrad Rzeszutek Wilk
2013-07-19 19:04     ` Olaf Hering
2013-07-19 14:58   ` Brandon Philips
2013-07-19 18:19     ` Daniel Kiper
2013-07-19 15:12   ` Greg KH
2013-07-19 18:32     ` Daniel Kiper
2013-07-19 19:14       ` Greg KH
2013-07-19 20:58         ` H. Peter Anvin
2013-07-22 17:03           ` Daniel Kiper
2013-07-22 17:20             ` Eric W. Biederman
2013-07-22 18:24               ` H. Peter Anvin
2013-07-22 18:33                 ` Greg KH
2013-07-22 18:36                   ` H. Peter Anvin
2013-07-24  0:22                   ` [Xen-devel] " Matt Wilson
2013-07-24  0:40                     ` Greg KH
2013-07-24  7:49                       ` Eric W. Biederman

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=20130719131819.GC11233@debian70-amd64.local.net-space.pl \
    --to=daniel.kiper@oracle.com \
    --cc=brandon@ifup.org \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®