From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Matt Wilson <msw@amazon.com>, "H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xensource.com,
Daniel Kiper <daniel.kiper@oracle.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Brandon Philips <brandon@ifup.org>
Subject: Re: [Xen-devel] is kexec on Xen domU possible?
Date: Wed, 24 Jul 2013 00:49:25 -0700 [thread overview]
Message-ID: <87ob9so0sa.fsf@xmission.com> (raw)
In-Reply-To: <20130724004058.GA20327@kroah.com> (Greg KH's message of "Tue, 23 Jul 2013 17:40:58 -0700")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Tue, Jul 23, 2013 at 05:22:36PM -0700, Matt Wilson wrote:
>> On Mon, Jul 22, 2013 at 11:33:15AM -0700, Greg KH wrote:
>> > On Mon, Jul 22, 2013 at 11:24:46AM -0700, H. Peter Anvin wrote:
>> > > On 07/22/2013 10:20 AM, Eric W. Biederman wrote:
>>
>> Many Xen-based cloud providers provide a mechanism for users to boot
>> the kernels they want. For example you can use PV-GRUB on EC2
>> instances to boot a kernel that is stored within an AMI.
>>
>> For more info:
>> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedkernels.html
>
> Yes, that's quite true, but some don't, or they make it difficult to do
> so. Using kexec also allows you to "be the bootloader" and decide on
> _which_ kernel you want to boot, independant of what cloud provider you
> use, something that lots of people want in their quest to not dependant
> on any one company.
I would be more than happy to review and help get something merged that
sorts out kexec on Xen.
Eric
prev parent reply other threads:[~2013-07-24 7:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 2:06 is kexec on Xen domU possible? 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
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 [this message]
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=87ob9so0sa.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=brandon@ifup.org \
--cc=daniel.kiper@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msw@amazon.com \
--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