From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Eric Biederman <ebiederm@xmission.com>,
Brandon Philips <brandon@ifup.org>
Subject: Re: is kexec on Xen domU possible?
Date: Fri, 19 Jul 2013 13:58:05 -0700 [thread overview]
Message-ID: <51E9A85D.2060206@zytor.com> (raw)
In-Reply-To: <20130719191449.GA1882@kroah.com>
On 07/19/2013 12:14 PM, Greg KH wrote:
>>
>>> The errors that the kexec tools seem to run into is finding the memory
>>> to place the new kernel into, is that just an issue that PV guests
>>> aren't given enough kernel memory in which to replicate themselves from
>>> dom0?
>>
>> There are a lot of differences between baremetal machines and PV guests.
>> For example you are not able to do identity mapping per se in PV guests.
>> Arguments to new kernel are passed in completely different way. etc.
>
> Ok, thanks for confirming that it is possible, but doesn't currently
> work for pv guests.
>
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.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
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 13:58:05 -0700 [thread overview]
Message-ID: <51E9A85D.2060206@zytor.com> (raw)
In-Reply-To: <20130719191449.GA1882@kroah.com>
On 07/19/2013 12:14 PM, Greg KH wrote:
>>
>>> The errors that the kexec tools seem to run into is finding the memory
>>> to place the new kernel into, is that just an issue that PV guests
>>> aren't given enough kernel memory in which to replicate themselves from
>>> dom0?
>>
>> There are a lot of differences between baremetal machines and PV guests.
>> For example you are not able to do identity mapping per se in PV guests.
>> Arguments to new kernel are passed in completely different way. etc.
>
> Ok, thanks for confirming that it is possible, but doesn't currently
> work for pv guests.
>
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.
-hpa
next prev parent reply other threads:[~2013-07-19 20:58 UTC|newest]
Thread overview: 36+ 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 2:06 ` Greg KH
2013-07-19 13:18 ` Daniel Kiper
2013-07-19 13:18 ` Daniel Kiper
2013-07-19 13:54 ` Konrad Rzeszutek Wilk
2013-07-19 13:54 ` Konrad Rzeszutek Wilk
2013-07-19 19:04 ` Olaf Hering
2013-07-19 19:04 ` Olaf Hering
2013-07-19 14:58 ` Brandon Philips
2013-07-19 14:58 ` Brandon Philips
2013-07-19 18:19 ` Daniel Kiper
2013-07-19 18:19 ` Daniel Kiper
2013-07-19 15:12 ` Greg KH
2013-07-19 15:12 ` Greg KH
2013-07-19 18:32 ` Daniel Kiper
2013-07-19 18:32 ` Daniel Kiper
2013-07-19 19:14 ` Greg KH
2013-07-19 19:14 ` Greg KH
2013-07-19 20:58 ` H. Peter Anvin [this message]
2013-07-19 20:58 ` H. Peter Anvin
2013-07-22 17:03 ` Daniel Kiper
2013-07-22 17:03 ` Daniel Kiper
2013-07-22 17:20 ` Eric W. Biederman
2013-07-22 17:20 ` Eric W. Biederman
2013-07-22 18:24 ` H. Peter Anvin
2013-07-22 18:24 ` H. Peter Anvin
2013-07-22 18:33 ` Greg KH
2013-07-22 18:33 ` Greg KH
2013-07-22 18:36 ` H. Peter Anvin
2013-07-22 18:36 ` H. Peter Anvin
2013-07-24 0:22 ` [Xen-devel] " Matt Wilson
2013-07-24 0:22 ` Matt Wilson
2013-07-24 0:40 ` Greg KH
2013-07-24 0:40 ` Greg KH
2013-07-24 7:49 ` Eric W. Biederman
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=51E9A85D.2060206@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 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.