From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: kexec and kdump on Xen?? Date: Thu, 17 Apr 2014 11:01:31 +0100 Message-ID: <534FA67B.2010805@citrix.com> References: <20140414081126.GA1632@router-fw-old.local.net-space.pl> <20140414132632.GA6173@router-fw-old.local.net-space.pl> <20140416111005.GA6251@router-fw-old.local.net-space.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Zhang, Yang Z" Cc: "xen-devel@lists.xen.org" , Daniel Kiper List-Id: xen-devel@lists.xenproject.org On 17/04/14 02:19, Zhang, Yang Z wrote: > > After investigation, I found some bugs (One is the segment overlap > check failure and another one is related to x2apic). With some > workarounds, now I am able to kexec from Xen into Linux. But it still > fails to run kdump(Xen->linux). I add some debug messages in the key > code path. It shows kexec_reloc() will cause machine reboot. Is it a > known issue? Rebooting after the kexec_reloc() call could be triggered from Xen, purgatory or the kernel. Can you turn on purgatory debug output (--console-serial --serial-baud=115200 options to kexec for serial) and earlyprintk in the kernel? You may also want to specify a crashregion location. e.g., we use the Xen option "crashkernel=128M@32M". David