From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Greg KH <gregkh@linuxfoundation.org>,
Daniel Kiper <daniel.kiper@oracle.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Brandon Philips <brandon@ifup.org>
Subject: Re: is kexec on Xen domU possible?
Date: Mon, 22 Jul 2013 11:24:46 -0700 [thread overview]
Message-ID: <51ED78EE.9020903@zytor.com> (raw)
In-Reply-To: <87wqoise9d.fsf@xmission.com>
On 07/22/2013 10:20 AM, Eric W. Biederman wrote:
>>>
>>> Also, in any virtualized environment the hypervisor can do a better job
>>> for things like kdump, simply because it can provide two things that are
>>> otherwise hard to do:
>>>
>>> 1. a known-good system state;
>>> 2. a known-clean kdump image.
>>>
>>> As such, I do encourage the virtualization people to (also) develop
>>> hypervisor-*aware* solutions for these kinds of things.
>>
>> In general I agree but if you could not change hypervisor
>> and/or dom0 (e.g. you are using cloud providers which are
>> stick to old versions of Xen) then you have no choice.
>
> Which tends to be where kexec on panic comes in most cases. Getting
> platform vendors to do something sane tends to be a multi-year political
> effort of dubious worth while just solving the problem locally actually
> gets the problem solved for those who care.
>
It should not be a "one or the other" issue.
-hpa
next prev parent reply other threads:[~2013-07-22 18:24 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 [this message]
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=51ED78EE.9020903@zytor.com \
--to=hpa@zytor.com \
--cc=brandon@ifup.org \
--cc=daniel.kiper@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).