From: Daniel Kiper <daniel.kiper@oracle.com>
To: Brandon Philips <brandon@ifup.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Eric Biederman <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
virtualization@lists.linux-foundation.org
Subject: Re: is kexec on Xen domU possible?
Date: Fri, 19 Jul 2013 20:19:46 +0200 [thread overview]
Message-ID: <20130719181946.GG11233@debian70-amd64.local.net-space.pl> (raw)
In-Reply-To: <CAK7GKxnB933DkO8qM6HxZCbDVNn4ze5Ere7ZWnXxBieYMg88dQ@mail.gmail.com>
On Fri, Jul 19, 2013 at 07:58:40AM -0700, Brandon Philips wrote:
> On Fri, Jul 19, 2013 at 6:18 AM, Daniel Kiper <daniel.kiper@oracle.com> wrote:
> > - 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,
>
> To do kexec on PV guests is there a dependency on support from the dom0?
No.
> e.g. if we recreated your patches and merged them into 3.12 and booted
> on a XenServer from a few years ago would it work?
No.
> What I want to do is use kexec on existing public cloud providers,
> that use Xen, like AWS or Rackspace.
Look for HVM or PVonHVM guests support in this providers.
Sadly, there is no support for kexec on PV guests.
Daniel
next prev parent reply other threads:[~2013-07-19 18:20 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
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 [this message]
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=20130719181946.GG11233@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®