From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: x86-64/kexec: crashkernel= without @xM suffix Date: Fri, 30 Apr 2010 07:42:06 +0100 Message-ID: <4BDA97DE0200007800000C43@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Was this ever tested by anyone? Has it ever worked with any Linux as secondary kernel? We're getting reports (and analysis confirms this) that the fact that Xen places the hole at the highest suitable address below 4G prevents kexec from working. A possible fix is non-obvious, since there doesn't appear to be a hard boundary below which the hole must reside (especially for a 32-bit secondary kernel; for a 64-bit one it seems like any place below 2G would be acceptable). Simply using Linux' strategy and allocating at the lowest possible address doesn't seem too nice a solution either, as we try to conserve on the use of low memory as much as possible almost everywhere else. Thanks, Jan